Jonathan Feally wrote:
Simon Gray wrote:
Michael Monnerie wrote:
Note:
Everybody who care about their data, you should leave this setting on
it's default "1":
innodb_flush_log_at_trx_commit=1
Also, this will only affect writes - rather than reads.
If you have minimal writes and the server is on a UPS, this setting
won't make too much difference, but if you have a lot of messages coming
in, then a setting of 1 would be safer, but further reduce read
performance under a mixed load.
Yes, assuming you don't separate your data types.
Moving towards 2.3.x should lend some
speed increases depending on what searching you are doing. If you are
searching single folders, then reducing the number of messages in each
folder will help speed it up. Moving messages by date received to a
sub-folder of year, quarter, or month can make a big difference. Bigger
mailing lists I use by month "2009-09_Sep" to keep the message count <
10k per folder.
Good to hear 2.3 should improve things.
I agree that the majority of your problems lie in disk i/o bandwidth.
Use a good hardware raid 10 (not a fake hardware raid that is really
software aka promise sata) with disks that have low seek times, a larger
on disk buffer, and good sustained read throughputs. You should never
use a raid5 for a database as the write performance will be very poor
when writing out data that is less than the stripe size, causing all
disks to be read, computed, then written to the affected disks.
This depends, raid 5 yelds more spindles to read from - but does have
the parity overhead on writes. Depends on your environment.
S
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
