Forum Moderators: open
Always on a MySQL DB:
I'm already have the conviction that the innoDb type is the solution because of transactions.
but i discover than :
performance == MyISAM and reliability == innoDB
a quick quiz:
-------------
.- how much differences exists respect performance?
.- can both types work inside one query?
.- read operations like SELECT have same performance in both types?
.- in a site with high traffic, performance in both types tends to equal?
.- I think than "row level locking" is better than "table level locking" over high traffic sites. correct?
that it is by the moment.-
TIA, NomikOS
---
comments or suggests please!
Just a few quick points on performance. Tuning and optimisation can be done:
- on the infrastructure level, such as fast disks and large cache memory
- on the datamodel level: revisiting your relations, indexes, table-layout etc can reveal some bottlenecks
- on the query level: explain plans, table optimisations, order in the WHERE -clause etc
I am not familiar with InnoDB, but if you have no need for transactional functionality, you may as well go with MyISAM and look closely at how your total DB-application functions and eke out performance gains from there.
Hope this helps
Tech
Remember that with MySQL you could choose to use MyISAM and InnoDB tables together.
You may want a fast MyISAM tables for logging clicks, tracking and you may even choose to use it on large tables rarely updated. These tables are fast & small, but shouldn't be mixed with InnoDB tables within Transactions, as they're updated immediately.
On the other hand the large, slower InnoDB tables are an extreamly safe way to hold data and you can use Transactions + various other sql features. But in the world of SQL databases InnoDB is very fast, it's just that MyISAM is even faster.
This discussion should may continue, right?
thanks all! I've what i need it.
---