Forum Moderators: open

Message Too Old, No Replies

performance == myisam v/s reliability == innoDB

about transactions

         

NomikOS

8:35 pm on Nov 9, 2005 (gmt 0)

10+ Year Member



I came from here [webmasterworld.com...] for continue a matter of your concern.

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!

technossomy

10:26 am on Nov 10, 2005 (gmt 0)

10+ Year Member



Hi NomikOS

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

jezzer300

11:05 pm on Nov 12, 2005 (gmt 0)

10+ Year Member



Hi there.

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.

NomikOS

3:44 am on Nov 13, 2005 (gmt 0)

10+ Year Member



jezzer300:
is the very first answer than i like it.
in this last days i learned enough about transactions.
MyISAM v/s innoDB is still a question unsolved.
but:
innoDB => "Code running reliable"
and came from here: [webmasterworld.com...]
so:
innoDB is the solution.

This discussion should may continue, right?

thanks all! I've what i need it.

---

dmmh

10:19 am on Nov 13, 2005 (gmt 0)

10+ Year Member



I use a mixture of both tbh. My main tables are all INNODB, the ones of lesser importance are MyISAM

and make sure indexes are ok, stuff like that

I would chose reliability over speed any day....