•
•
•
•
What is DaniWeb IT Discussion Community?
You're currently browsing the MySQL section within the Web Development category of DaniWeb, a massive community of 374,460 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 2,769 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Please support our MySQL advertiser:
Views: 38438 | Replies: 21
 |
•
•
Join Date: Feb 2008
Posts: 1
Reputation: 
Rep Power: 0
Solved Threads: 0
Newbie Poster
Hi
I have been researching the differences (implementation as well as performance) between MyISAM and InnoDB for sometime. It looks like we need to hit a subtle balance between both of them,
In particular, it was very disappointing for me to read that Dani had to revert back from InnoDB.
The right way to use the mix, IMO, is to use a master-slave configuration for database replication. One should use InnoDB on the master to store tables for fast concurrent inserts and updates. The same table should be replicated on the slave using MyISAM for fast reads.
Also, when using InnoDB, don't forget to play around with the innodb_buffer_pool and innodb_thread_concurrency parameters. They seriously impact the performance you get out of InnoDB setup.
One last point to note here is that InnoBase has been acquired by Oracle already. So, future bug fixes and improvements may not be free.
Hope this helps!!
I have been researching the differences (implementation as well as performance) between MyISAM and InnoDB for sometime. It looks like we need to hit a subtle balance between both of them,
In particular, it was very disappointing for me to read that Dani had to revert back from InnoDB.
The right way to use the mix, IMO, is to use a master-slave configuration for database replication. One should use InnoDB on the master to store tables for fast concurrent inserts and updates. The same table should be replicated on the slave using MyISAM for fast reads.
Also, when using InnoDB, don't forget to play around with the innodb_buffer_pool and innodb_thread_concurrency parameters. They seriously impact the performance you get out of InnoDB setup.
One last point to note here is that InnoBase has been acquired by Oracle already. So, future bug fixes and improvements may not be free.
Hope this helps!!
|
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
•
•
•
•
•
•
•
•
DaniWeb MySQL Marketplace
Linear Mode
Other Threads in the MySQL Forum
- Previous Thread: SQL query program to edit records
- Next Thread: Help please
