Showing entries 1 to 4
Displaying posts with tag: LRU dump (reset)
LRU followup #2

As I wrote in the previous LRU followup the innodb_lru_dump_restore directive has the drawback that it only loads the LRU dumpfile after starting up. I’m happy to say that I’m not the only one who noticed that: Vadim Tkachenko noticed the same a few months back when he was integrating Galera replication and he filed a bugreport for it.

It now has been resolved as of Percona Server 5.1.59-13.0 and 5.5.16-22.0 (both released this morning) with the configuration directive innodb-blocking-lru-restore.

However the …

[Read more]
LRU follow up

Due to one of the machines being configured a little bit too close to the edge we had to restart it to downsize its innodb_buffer_pool_size a little bit. We tested the innodb_lru_dump_restore directive with this machine. Results were very promising: it wrote the dump every 5 minutes (we set the variable to 300 seconds) and after MySQL had restarted it reloaded the dump.

However: since MySQL is already started fully before it even starts to load the LRU dump it means MySQL is already available to the outside world. This means in a HA environment it would already be going to perform poorly due to the torrent of queries coming in. This means either the loading of the LRU dump needs to be done up front by a change in Percona Server or we need to alter MMM not to do anything with the server untill it has loaded the LRU dump.

Challenges, challenges…

Tagged: …

[Read more]
LRU Dump restore

Yesterday one of my colleagues pointed me to the innodb_lru_dump_restore variable available in the Percona MySQL Server distribution. See more about it here:
LRU meaning that the list is in Least Recently Used order to make it easier to remove old items off the pages. Reading from the description it can be a very nice option for already running servers to maintain this list after startup, but it did not solve my immediate problem: I had to warm up two new freshly cloned read slaves on one of our busiest databases.

Normally I use mk-query-digest with the –processlist option on the (active) master, but in our setup this is seriously flawed because you will only replay the slow running queries …

[Read more]
Percona Server Fast-Restart White Paper Posted

I’ve posted a new white paper about the implementation and benefits of Percona Server’s fast-restart capabilities. Briefly, after shutting down and restarting or rebooting the server, it can be back to full performance in a couple of minutes. That’s minutes, not hours or days. This matters a lot for keeping uptime high and reducing hardware requirements. There are a ton of benefits when you don’t have to obsess over how long it’s going to take to get the server back into production. Hot buzzword-compliant use cases definitely include cloud computing, because now you can get lots of memory in the cloud, but you still get terrible I/O performance so MySQL restarts take an eternity.

Read the white paper for the details; it is posted in the white paper section of our site and as always, is free to download and share with friends.

Showing entries 1 to 4