Comments on: Choosing innodb_buffer_pool_size

By: Detecting and Resolving LAMP Stack Problems – Scheduled Downtime » Karl Katzke | PHP, Puppies, and other Geekery

Thu, 15 Oct 2009 04:51:30 +0000

[...] time, especially when some of your tables are larger than 1gb.) Don’t forget to switch to set innodb_buffer_pool_size [...]

By: Tuning a Linux system for Database Server | Random Bugs

Tuning a Linux system for Database Server | Random Bugs — Thu, 16 Jul 2009 17:31:58 +0000

[...] more info read: http://www.mysqlperformanceblog.com/2007/11/03/choosing-innodb_buffer_pool_size/ [...]

By: SQL Dan

SQL Dan — Sun, 14 Jun 2009 04:35:34 +0000

Is the INNODB_BUFFER_POOL shared across all databases or allocated per database? I’m getting ready to run a mysql server in a VMWare environment with a not very busy database. Maybe 10 concurrent users max. With about 5000 records being added per year max per database. I was thinking about running the virtual OS with 2GB of RAM.

By: [译]Innodb 性能优化基础 | 白天’s Blog

[译]Innodb 性能优化基础 | 白天’s Blog — Sun, 19 Apr 2009 14:51:19 +0000

[...] UPDATE 关于它具体的查看http://www.mysqlperformanceblog.com/2007/11/03/choosing-innodb_buffer_pool_size/ innodb_log_file_size [...]

By: ［翻译］［注解］Innodb Performance Optimization Basics | 白天’s Blog

［翻译］［注解］Innodb Performance Optimization Basics | 白天’s Blog — Sun, 19 Apr 2009 14:47:35 +0000

[...] innodb_buffer_pool_size 设为内存的70%-80%都是安全的。我在一个16G的服务器上把它设成12G。 UPDATE：如果你想了解更多的细节，请查看tuning innodb buffer pool [...]

By: Alex

Alex — Mon, 30 Mar 2009 23:14:33 +0000

I now realize I know absolutely nothing about MySQL. Thanks for all the info (book and blog).

By: Cristian

Cristian — Thu, 26 Feb 2009 10:15:25 +0000

My server configuration
2GB /intelquad

PROBLEM : i start my sql 4.0.12 with innodb_buffer_pool_size = 128
After starting the server my.cnf becomes my_cnf.bak.

but randomly the configuration is reseted and all my previous config is set to the default values inlcuding innodb_buffer_pool_size which is set to 5Mb or so

This happes only since this week.

Do you know what to do ?

I am kind of very stressed due to this .

I can;t migrate now to other version of mysql.

By: Baron Schwartz

Baron Schwartz — Wed, 14 Jan 2009 19:23:32 +0000

I haven’t seen this in the real world, but I don’t disbelieve you. If you want help solving this, I am pretty confident we can find out what is going on and either find a workaround or discuss the possibility of a patch. You could also try a bug report via MySQL, but I don’t know how urgent this is for you to solve.

By: zhang

zhang — Wed, 14 Jan 2009 16:11:22 +0000

That’s exactly the reason I brought it up here. 5.0.67 and 5.0.67 with google patch do NOT have this behavior. The response time stabilized after the buffer pool is full.
Seems like 5.1 has problems to manage eviction.

By: Baron Schwartz

Baron Schwartz — Tue, 13 Jan 2009 20:22:12 +0000

This is easy to explain as flushing dirty pages to make some room for pages that aren’t in the buffer pool. Watch the number of *dirty* pages. Compare that to innodb_buffer_pool_max_dirty_pct.

Is this specific to 5.1? Have you see it behave differently on 5.0? I would expect to see the same behavior in 5.0, but tell me if I’m wrong.