I have these, dunno how optimized / non-default they are, but works well: key_buffer = 16M max_allowed_packet = 4M # Robbie: larger packet sizes. table_cache = 64 sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 8M
And as for InnoDB, I cranked everything up like crazy, and basically get most of my database in memory. If you have 4GB of RAM, I think it's entirely reasonable to put a gig into MySQL buffering. But, again, no hard numbers to back these up :-\ innodb_buffer_pool_size = 640M # huge buffer! innodb_additional_mem_pool_size = 120M # huge buffer! #innodb_data_file_path = ibdata1:10M:autoextend:max:128M # larger everything for InnoDB innodb_data_file_path=ibdata1:500M;ibdata2:250M:autoextend On Tue, 2006-10-24 at 23:26 -0700, kbaker wrote: > We are finally releasing our production DBMail system. > > I would like to make some optimizations to MySQL to ensure best performance. > > Could you give me some general guidelines for setting my.cnf to work best > with > DBMail? > > I know there are plenty of books on this.. but thought maybe you could give > some > general guidelines since you've probably done some load testing. > > 4GB's Ram dual proc machines > > We are running MySQL 4. > > - max_connections - We have at 500, is there some sort of formula for this. > should it be based on the amount of ram we have? > - query_caching - Set at 16MB. Again I was thinking this would be based on RAM > but all the examples I've seen use 16MB. > > > > > Thanks any info would be great, > > - Kevin > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev
