Is it just not the case that InnoDB table have to do more as they have moreNot exactly.
functionality and so take more time?
InnoDB does indeed support transactions, uses the ultimate in concurrency control (multiversioning) and provides foreign key constraints.
That said, MyISAM provides FULLTEXT searches and OpenGIS-style storage in 4.1.x.
Having the choice between MyISAM and InnoDB is one of MySQL's primary strengths. In many cases, InnoDB will actually be faster due to many of the cutting edge methods that InnoDB possesses but MyISAM does not. For other workloads, MyISAM will be faster as it doesn't need to worry about rolling things back or having multiple updates from different connections to keep track of the state of to any large degree.
Regards,
Chris
Simon
----- Original Message ----- From: "Jiří Matějka" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 18, 2004 10:38 AM
Subject: Speed of MyISAM vs. InnoDB
toHi all, I'm using mysql 4.0.17 and I have this problem with speed of innodb database:
I have simple command like select count(*) from table1, or select field1,
field2 from table1. The table1 and has more than cca 10.000 rows (most of
the fields are integer, only several varchars and several memos) and its
type is InnoDB. Then the query lasts too long, at least several seconds,
sometimes more than 5. If I convert it to MyISAM then the query lasts
usually less then 0.3 second. If the table is small (cca less than 5.000
rows) then there is not big difference...
Is it normal, that InnoDB isn't able to access large table as quickly as
MyISAM? Or is there any parametr to set to make InnoDB run faster? I need
use InnoDB because it supports transactions and MyISAM not...
thx
Jiri Matejka [EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
