I'm not 100% sure, but I think these are MyISAM only. I think the
roughly equivalent InnoDB setting is:
innodb_buffer_pool = 1024M
It is myisam only, use buffer_pool instead.
Another thing that is worth doing is bypassing OS caching for table
access because MySQL does it's own caching, and is much more efficient
than the generic OS algorithm:
innodb_flush_method=O_DIRECT
As long as you have a decent raid card with a bbu. You should be careful
with these options, they can actually reduce performance, its best to
benchmark and see which performs best on your hardware.
max_connections = 1800
You might want to watch out for the max connections - can you server
actually handle 1800 connections? remember for each connection, you'll
have all the relevant buffers/memory in place. You'll probably find your
server runs out of memory and swaps before it hits 1800 connections.
Its worth looking at innodb_flush_log_at_trx_commit=0/2
- http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html
It'll reduce your disk i/o slightly for log writes. You may want to
separate your data from your logs and os. Logs are sequential, data is
random - you can optimise each accordingly.
Also, to answer the first question about the performance - it may be
worth looking towards imapproxy - it helps reuse existing connections,
rather than opening a new one each time (particularly with webmail) and
waiting for the connection to timeout - it might help with your scenario.
Paul is working on the new threading model, which will help dbmail's
performance dramatically. Look at the dev list for more info.
Regards,
SG
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
