|
Re: Sorting out mysqld options: msg#00131gnome-infrastructure
Owen Taylor wrote: The value I'm least sure about is innodb_file_per_table; it's also It's best to keep it on, for Bugzilla. It won't have any significant performance impact, and it will allow InnoDB to more effectively reclaim space in its data files if needed. If you had a heavy-write application with 1000 tables, I'd suggest keeping it off, because the tiny tiny overhead of the extra fsync calls would possibly add up if you were looking at 2500 transactions per second or something like that. log_slow_queries You might want to set slow_query_time (or whatever the var is called) down to 6--that will be more likely to show up truly slow queries. innodb_buffer_pool_size Bugzilla of course won't use all that, but I'm assuming you're setting it that high because there will be other applications using InnoDB on this server. key_buffer_size I'm doing a test upgrade right now, and once it's done I'll let you know how large the indexes are on the bugs_fulltext table. read_buffer_size If you search short_desc for a substring, you're likely to do one, because MySQL can't use indexes in that case. Note this, however: http://www.mysqlperformanceblog.com/2007/09/17/mysql-what-read_buffer_size-value-is-optimal/ -Max -- Max Kanat-Alexander Chief Engineer http://www.everythingsolved.com/ Everything Solved: Complete Computer Management _______________________________________________ gnome-infrastructure mailing list gnome-infrastructure@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gnome-infrastructure
|
|
||||||||||||||||||||||||||
|
|
|
| News | Mail Home | sitemap | FAQ | advertise |