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: optimizations (reset)

Spreading .ibd files across multiple disks; the optimization that isn’t
+1 Vote Up -0Vote Down
posted by Morgan Tocker of team blog MySQL Performance Blog on Sat 25 Dec 2010 16:50 UTC
Tags:
(edit) mysql, tips, innodb, lvm, Backups, innodb_file_per_table, optimizations, silly advice given

Inspired by Baron's earlier post, here is one I hear quite frequently -

"If you enable innodb_file_per_table, each table is it's own .ibd file.  You can then relocate the heavy hit tables to a different location and create symlinks to the original location."

There are a few things wrong with this advice:

  • InnoDB does not support these symlinks.  If you run an ALTER TABLE command, what you will find is that a new temporary table is created (in the original location!), the symlink is destroyed, and the temporary table is renamed.  Your "optimization" is lost.
  • Striping (with RAID) is usually a far better optimization.  Striping a table across multiple disks effectively balances the  'heavy
    •   [Read more...]
    SHOW ENGINE INNODB STATUS;
    +0 Vote Up -1Vote Down
    posted by Jayant Kumar on Fri 02 Oct 2009 10:40 UTC
    Tags:
    (edit) mysql, innodb, optimizations, optimize mysql
    Innodb monitors show information about innodb internal status - which could be used for performance tuning. Lets break down the output of show engine innodb status and get a look at what is happening and how it can be improved. Just fire the "Show engine innodb status" command and check the Output.mysql> show engine innodb status\G*************************** 1. row ***************************
    optimizing mysql guide
    +0 Vote Up -1Vote Down
    posted by Jayant Kumar on Thu 11 Jun 2009 04:55 UTC
    Tags:
    (edit) mysql, optimizations, optimize mysql
    I had written about this but mostly in parts. Here is a step by step guide to optimizing mysql. Following variables should be looked into for optimizing mysql.Memory consumption: Total memory consumption should be less than the available RAM. You should also leave a small amount of memory for the OS. Total memory consumption can be calculated using this formula (for myisam tables):Key_buffer + (
    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.