…ON MEM=12G innodb_thread_concurrency=20 innodb_buffer_pool_size=3G =================================================== =================MySQL error log=================== 060804 20:….ibd files… InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer… 060804 21:29:29…
Post: Percona Server 5.5.16-22.0
…-blocking-buffer-pool-restore (in 5.1 it is –innodb-blocking-lru-restore), which is OFF by default. When set to ON, restoring from the… boolean option, –innodb-blocking-lru-restore, which is OFF by default. When set to ON, restoring from the LRU dump file is…
Post: InnoDB: look after fragmentation
…,351,616 bytes on disk The problem is that after restoring table from mysqldump, the query that scans data by primary… hurt your query significantly, especially when data is not in buffer_pool and execution goes to read from disk Fragmentation by secondary…
Post: MySQL Crash Recovery
…. As I already wrote innodb_log_file_size and innodb_buffer_pool_size affect recovery time significantly as well as your workload… Start – If you restart MySQL server its caches (key_buffer, innodb_buffer_pool, query_cache,table_cache) are cleaned, so may be OS… problems which you may experience related to MySQL Crash Recovery – Restoring data from backup, corrupted Innodb tablespace recovery etc but I…
Comment: How to change innodb_log_file_size safely
… my.ini innodb_buffer_pool_size = 256M innodb_additional_mem_pool_size = 8M innodb_log_file_size = 64M innodb_log_buffer_size = 8M innodb… from the .ibd files… InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer… 130319 0:10:26 InnoDB: Started…
Post: How innodb_open_files affects performance
… pages in innodb buffer pool which had to be flushed before recycling. First ran however was done with clean buffer pool (after reading all… information from the .ibd files… InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer… InnoDB: Doing recovery: scanned up…
Comment: Percona Server 5.1.50-rel12.1
Wow, the buffer pool dump/restore feature is something I will definitely check out! Restarting a machine with 60GB+ of buffer pool just takes forever to warm back up again. I’m in the early stages of upgrading ~50 database machines from 5.0 to 5.1 and this looks like another great reason to do it.
Post: FlashCache: more benchmarks
…, as there is no way to recovery from that ( only restore from backup). I personally did couple of power failure tests… for cache on SSD and I used 16GB and 10GB buffer pool sizes. I run sysbench with special distribution, not uniform, the…/wiki/benchmark:flashcache:sysbench:300mln_rows:start And short results: buffer_pool, GBRAID10 FlashCache 20% 16468.76985.47 10328.34704.36 As…
Comment: XtraDB feature: save / restore buffer pool
Vadim, how does this interact with recovery? Does it work OK if you save the buffer pool contents, then crash the server, restart it, and restore the buffer pool? If not, then that might be a problem for the DRBD use case. I think it should work fine, but maybe I’m wrong.
Comment: Is DRBD the right choice for me?
…-more-usable-innodb-saverestore-buffer-pool-patch/ If the idea he mentioned “Add runtime commands to save/restore the buffer pool state from a running…

