  | |  | Controlling memory usage under Win32: query_cache_size or innodb_buffer_pool_siz | Controlling memory usage under Win32: query_cache_size or innodb_buffer_pool_siz 2004-12-21 - By Patrick Questembert
Back When I run large queries, mysqlnt.exe gets to around 150MB of memory usage, which brings my WinXP server to a near stand-still and other apps are barely able to run ...
This is on Windows XP, MySQL Server 4.1, 1GB of memory, all tables InnoDB. I am running 3 MySQL apps (which are not querying lots of data, just writing) and one app querying a large number of rows.
I haven't tuned my MYSQL server performance just yet so would appreciate some guidance to avoid tuning the wrong parameter ... which of the size parameters do I need to change for this situation?
I assume I need to edit \Program Files\MySQL\MySQL Server 4.1\my.cnf The size parameters mentioned there in relation to InnoDB tables are: query_cache_size=33M tmp_table_size=16M (not sure if this is relevant for apps which don't create in-memory tables explicitely) innodb_additional_mem_pool_size=2M (recommended not to change this value) innodb_log_buffer_size=1M innodb_buffer_pool_size=93M innodb_log_file_size=19M
At first glance, query_cache_size=33M or innodb_buffer_pool_size=93M seem like the parameters I need to tune down. Question is which one? In-line documentation of both parameters seem to indicate an overlap in purpose ... does innodb_buffer_pool_size supercede query_cache_size for InnoDB tables?
Thanks! Patrick Questembert
-- MySQL Windows Mailing List For list archives: http://lists.mysql.com/win32 To unsubscribe: http://lists.mysql.com/win32?unsub=mysql@(protected)
Earn $52 per hosting referral at Lunarpages.
|
|
 |