[solved] Performance using INT/SMALLINT

MySQL & MariaDB Other MySQL® Questions
1

Hi!
Perhaps this is a question for INTEL or likewise but i figured someone would know.

I nag about using apropriate type for integer (and other). Don’t use INT when TINYINT is enaugh. That way storage space is saved.
But last week someone mentioned that what you win in storage is lost in execution.

INT require 4 bytes and SMALLINT 2 bytes. The theory was that it’s faster to calculate with 4 bytes than with 1, 2 or 3 bytes and that the processor (?) anyway padds (or truncate) the value to 4 bytes.

Something to do with 32-bit processor and that 32/2=> 16/2=8

Anyone who can explain this?

Rgds
thomas

2

Do not mix storage and computation.

Computation is always done using signed 64bit integer in MySQL (even for 32bit)

3

Ok, so computing don’t get affected by the fact that i store a value as INT or SMALLINT?

4

Thanks!
Btw, great blog and forum!!!