Now I found one more "strange" thing - if I use show tables to get table properties, then if table is MyISAM the number of rows is correct and if it is InnoDB number of rows is around 2000 lower... And the innodb table looks 8 times bigger than myisam table (field data_length in show table status query)...
Jiri Matejka [EMAIL PROTECTED] ==>Wednesday, February 18, 2004 11:57 AM [EMAIL PROTECTED] wrote: > I think count(*) is a special case: MyISAM holds a record count which > it can access instantly, InnoDB has to count rows. Does the time > difference persist for real queries? > > Alec > > Jiří Matějka <[EMAIL PROTECTED]> wrote on 18/02/2004 10:38:13: > >> Hi 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 to use InnoDB because it supports transactions >> and MyISAM not... -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
