Home |  MySQL Buzz |  FAQ |  Feeds |  Submit your blog feed |  Feedback |  Archive |  Aggregate feed RSS 2.0 English Deutsch Español Français Italiano 日本語 Русский Português 中文
Showing entries 1 to 3

Displaying posts with tag: buffer pool (reset)

When EXPLAIN estimates can go wrong!
+0 Vote Up -0Vote Down
posted by Ovais Tariq on Sun 16 Oct 2011 19:32 UTC
Tags:
(edit) mysql, MySQL 5.1, select, execution plan, explain, indexes, query execution, MySQL 5.5, buffer pool, range scan, mysql bug, estimates, estimation, index pages, index tree, innodb_stats_sample_pages, simple select
This is the title of my first blog post on MySQL Performance Blog. It deals with a customer case where the customer was facing a peculiar problem where the rows column in the EXPLAIN output of the query was totally off. The actual number of rows was 18 times more than the number of rows reported by MySQL in the output of EXPLAIN. Now this can be a real pain as MySQL uses “the number of rows” estimation to pick and choose indexes and it could really be picking up a wrong index simply because of the wrong estimate. You...
Shortened warm-up times with a preloaded InnoDB buffer pool
Employee +7 Vote Up -0Vote Down
posted by John Russell on Mon 25 Jul 2011 20:53 UTC
Tags:
(edit) Uncategorized, performance, feature, InnoDB plugin, InnoDB Builtin, buffer pool

Are you running an InnoDB installation with a many-gigabytes buffer pool(s)? Does it take too long before it goes back to speed after a restart? If yes, then the following will be interesting to you.

In the latest MySQL 5.6 Labs release we have implemented an InnoDB buffer pool(s) dump and load to solve this problem.

The contents of the InnoDB buffer pool(s) can be saved on disk before MySQL is shut down and then read in after a restart so that the warm up time is drastically shortened – the buffer pool(s) go to the state they were before the server restart! The time needed for that is roughly the time needed to read data from disk that is about the size of the buffer pool(s).

Lets dive straight into the commands to perform various dump/load operations:

The buffer pool(s) dump can be done at any time when MySQL is

  [Read more...]
Why do I recommend switching over from MyISAM to Innodb!
+1 Vote Up -0Vote Down
posted by Ovais Tariq on Tue 16 Nov 2010 11:47 UTC
Tags:
(edit) mysql, innodb, performance, Backups, foreign keys, transactions, locking, recovery, acid, clustered indexes, concurrency, row-level locking, crash recovery, throughput, Hot Backup, database resources, mysql resources, acid-compliant, adaptive hash indexing, background flushes, buffer pool, change buffer, data consistency, innodb resources, innodb vs myisam, read ahead
Although MyISAM has been the default storage engine for MySQL but its soon going to change with the release of MySQL server 5.5. Not only that, more and more people are shifting over to the Innodb storage engine and the reasons for that is the tremendous benefits, not only in terms of performance, concurrency, ACID-transactions, foreign key constraints, but also because of the way it helps out the DBA with hot-backups support, automatic crash recovery and avoiding data inconsistencies which can prove to be a pain with MyISAM. In this article I try to hammer out the reasons why you should move on to using Innodb instead of MyISAM.
Showing entries 1 to 3

Planet MySQL © 1995, 2013, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.