Hi friends,
we're developing a new web application that works with a db around 1gb
and 30 tables.
We work with linux, and I'm evaluating the benefit of making an specific
partition (ext3) for mysql in order to have a bigger Block Size. Block
Size by default in / partition is 4096.
Do you think
Will you be using the MyISAM or InnoDB table engines?
I had heard that InnoDB uses 16k blocks internally, so that might be a good
starting point, though I'd love to have someone confirm or deny that this is
actually true.
-Aaron
On Fri, May 9, 2008 at 12:01 AM, Iñigo Medina García
[EMAIL
I would use as large a block size as you dare, especially with InnoDB.
Makes reading and writing faster as custs down seek time as cuts down
disk fragmenation and avoids block table reads. With MyIsam you have
lots of files, but if you only have a few again might work well with a
large
Thanks, Aaron.
Will you be using the MyISAM or InnoDB table engines?
Both, but InnoDB more.
I had heard that InnoDB uses 16k blocks internally, so that might be
a good starting point, though I'd love to have someone confirm or deny
that this is actually true.
Ok, that's interesting. :-)
Thanks Ben.
I would use as large a block size as you dare, especially with InnoDB.
Makes reading and writing faster as custs down seek time as cuts down
disk fragmenation and avoids block table reads. With MyIsam you have
lots of files, but if you only have a few again might work well with
I'm seeing that architecture has almost allways the limit in 4 kb (block
size - page). Theoretically architecture of 64 bits would offer up to 8
kb, but it seems to be that it usually has 4 kb too because of
compatibiliry issues with its i386 ancestors.
Any idea about that? We run Intel Core 2
Will you be using the MyISAM or InnoDB table engines?
I had heard that InnoDB uses 16k blocks internally, so that might be a good
starting point, though I'd love to have someone confirm or deny that this is
actually true.
Yep, Aaron. Look at: http://www.innodb.com/innodb/features/
and
That's true in some workloads, but with InnoDB you'll usually run into data
file fragmentation before filesystem fragmentation (unless it's a shared
system). This is especially true if your application runs a lot of updates
or deletes as random chunks of space will become free at different points
