Quote:
Originally posted by skazzel
I've been testing MySQL4 + InnoDB the past couple of weeks and it blows MySQL3+INNODB out of the water. The data below is on a server running MySQL3+INNODB doing about 500k hits / day. Tuning high load servers is an art.
|
Comparing MySQL4 + InnoDB with MySQL3+INNODB with no more information as to what you do with the DB has little vlaue.
For example, for a same row concurernt-writes intensive application MySQL3+innoDB will kick MySQL4+INNODB out of earth without hickups
You have to understand the difference between the different table handlers and database engines before commenting on those.
innoDB is good for same row writes (solving row-level locking with multi-versioning) or even general write intensive (solving table locking) where myISAM will have hard time performing (even with Delayed inserts)
INNODB is better for read intensive application. disk/memory space consumption of myISAM is much better than innoDB and therefore takes less IO and memory which is crucial in big/huge applications. There are more table handlers such as MERGE tables and HEAP tables an BerkleyDB that should be considered when implementing big projects. Just saying "MySQL4 + InnoDB blows MySQL3+INNODB" should not be taken too seriously by others. No offense meant, but i'm just warning people not to run and turn their tables into innoDB.
Same goes for mySQL 4.*. One should understand the differences before deciding what to do. On one hand, version 4 added query caching, which is ONLY good for read intensive (writ scarse) applications (it can even be a little damaging for write intensive applications if not tuned appropriately). Other features are also depending on what you do - such as sub-queries. If general, mySQL 4 might be a little slower (on some core functions) than version 3. due to added complexity/advancements in code base, but that is marginal. Biggest disadvantage so far is the fact that version 4 is not yet defined as release (still in Gamma). Looking at the change_log you could see alot of bugs are being corrected (showing its still a new and little-buggy system).
As skazzel said, its an a little of an art to fine-tune a high-load server BUT chosing the right table handlers and designing the database/tables and code right is MUCH MUCH MUCH more important. The tunning is the last step. There are good enough rule-of-thumb guide as to how to tune a high-load server with the mysql docs.
