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 4

Displaying posts with tag: innodb resources (reset)

Understanding InnoDB clustered indexes
+3 Vote Up -0Vote Down
posted by Ovais Tariq on Thu 20 Jan 2011 14:02 UTC
Tags:
(edit) innodb, performance, indexes, Clustering, primary key, clustered indexes, B-Tree, innodb resources, advantages, disadvantages, index storage, innodb indexes, secondary index
Some people don't probably know, but there is a difference between how indexes work in MyISAM and how they work in InnoDB, particularly when talking from the point of view of performance enhancement. Now since, InnoDB is starting to be widely used, it is important we understand how indexing works in InnoDB. Hence, the reason for this post!
Tuning InnoDB Configuration
+2 Vote Up -0Vote Down
posted by Ovais Tariq on Tue 21 Dec 2010 14:07 UTC
Tags:
(edit) mysql, innodb, configuration, performance, tuning, conf, transactions, acid, server, innodb_buffer_pool_size, innodb_flush_log_at_trx_commit, innodb_log_file_size, log file, innodb buffer pool, innodb_thread_concurrency, mysql resources, innodb resources, innodb log buffer, innodb log file, innodb thread concurrency
I had earlier written a post on tuning the MySQL server configuration which was more geared towards the MyISAM storage engine. While that is not because I didn't intend on ignoring InnoDB but because I had planned a whole post on tuning InnoDB related configuration. So this post is the post that I had planned, I have discussed the major configuration parameters in here that should help you out most of the times.
How to resize Innodb log files?
+1 Vote Up -4Vote Down
posted by Ovais Tariq on Tue 16 Nov 2010 13:03 UTC
Tags:
(edit) mysql, innodb, How To, innodb_log_file_size, log file, innodb resources, log file size, resize log file
Just in case you don't know resizing Innodb log file is not just simple as changing the value of innodb_log_file_size in the MySQL configuration file. But its even more simpler. Follow the steps in this post and you will be done with the resizing.
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 4

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.