Skip to main content
20 events
when toggle format what by license comment
S Mar 21, 2022 at 10:00 history suggested Spherical Cowboy CC BY-SA 4.0
Typo: innodb_io_capactity -> innodb_io_capacity
Mar 20, 2022 at 18:24 review Suggested edits
S Mar 21, 2022 at 10:00
May 23, 2017 at 12:40 history edited CommunityBot
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Apr 13, 2017 at 12:42 history edited CommunityBot
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
Jul 5, 2012 at 15:19 vote accept Don Wool
Jul 5, 2012 at 13:42 comment added Don Wool So you would set the pool_instances to each NUMA node, in this case, not each 'physical CPU'. ok. also read the Jeremy Cole blog piece referenced - which was fascinating but didn't see direct tie in to innodb_buffer_pool_instances, rather it seems piece addressed swappiness issue (brilliantly solved). Was it something someone said in the threads? Thx for all the help! --Don
Jul 5, 2012 at 11:25 comment added RolandoMySQLDBA Set innodb_buffer_pool_instances to 4 and set innodb_buffer_pool_size to 64G
Jul 5, 2012 at 3:42 comment added Don Wool NUMA output and physical CPU modules/dies have been detached from each other for a couple of generations of processor. His interpretation would be right in the first gen of multicore or anything with a hyperthreaded bus, but not so much with this stuff. Yes, it has 128GB.
Jul 5, 2012 at 3:42 comment added Don Wool It's actually 2 CPU modules, with eight total cores each. The scheduler treats them as 16 individual CPUs. In this generation of AMD processor, each module has two dies with four cores on each die. They go to some trouble to make each core as close to a full-fledged CPU with its own bus and cache, there is essentially no difference between 4x4, 2x8, or 16x1, except for cooling. On this sort of system, I have always tuned to the number of cores, not modules or dies.
Jul 5, 2012 at 3:41 comment added Don Wool Here is the response that I got back from my admin :
Jul 5, 2012 at 2:10 comment added RolandoMySQLDBA To me, output looks like quad-quad core (16 cores) using 4 CPUs. Therefore, set innodb_buffer_pool_instances=4. One more request: Please double check, does the DB server have 64GB or 128GB ???
Jul 5, 2012 at 1:12 comment added Don Wool Ok I posted the output of 'numactl' in the question.
Jul 4, 2012 at 22:23 comment added RolandoMySQLDBA Please run numactl --hardware and post the output in the question. I am trying to figure out physical CPUs and I want to make sure the admin isn't saying CPUs when he means cores.
Jul 4, 2012 at 21:42 comment added Don Wool regards innodb_buffer_pool_instances I have a 16-cpu box (I had thought it was 10). regards numactl my admin says "You have 16 total CPUs, and four blocks of RAM, 32G each. Each block of RAM is treated as local memory by four CPUs."
Jul 4, 2012 at 21:30 comment added Don Wool Thx for this incredibly useful reply!! I salute you. Regarding log size, do I have to worry about making it too big? my concern is something that Tkachenko wrote about mysqlperformanceblog.com/2011/09/18/disaster-mysql-5-5-flushing. I realize I am on Percona, so maybe this isn't a concern.. but I want to be sure I dont run into a stall scenario. I am digging into the rest of your reply...
Jul 4, 2012 at 20:20 history edited RolandoMySQLDBA CC BY-SA 3.0
added 16 characters in body
Jul 4, 2012 at 20:05 history edited RolandoMySQLDBA CC BY-SA 3.0
added 200 characters in body; added 124 characters in body
Jul 4, 2012 at 19:59 history edited RolandoMySQLDBA CC BY-SA 3.0
added 231 characters in body
Jul 4, 2012 at 19:53 history edited RolandoMySQLDBA CC BY-SA 3.0
added 260 characters in body; added 317 characters in body
Jul 4, 2012 at 19:44 history answered RolandoMySQLDBA CC BY-SA 3.0