List:General Discussion« Previous MessageNext Message »
From:Daniel Kasak Date:August 24 2005 10:45pm
Subject:Re: MyISAM vs. InnoDB for an AUTO_INCREMENT counter table
View as plain text  
Eamon Daly wrote:

> We have a table containing just one column that we use for
> unique IDs:
>
> CREATE TABLE `id_sequence` (
>  `id` int(10) unsigned NOT NULL auto_increment,
>  PRIMARY KEY  (`id`)
> ) TYPE=MyISAM
> Watching 'SHOW FULL PROCESSLIST' and reading the slow query
> log shows the occasional backlog of locks. Has anyone found
> significant speed increases or better concurrency by
> switching over to InnoDB for such a table?

I've found that MS Access will produce this behaviour ( among others ) 
when you get a number of clients connected to MyISAM tables. Converting 
to InnoDB solves it every time.

-- 
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak@stripped
website: http://www.nusconsulting.com.au
Thread
MyISAM vs. InnoDB for an AUTO_INCREMENT counter tableEamon Daly24 Aug
  • Re: MyISAM vs. InnoDB for an AUTO_INCREMENT counter tableSGreen24 Aug
    • Re: MyISAM vs. InnoDB for an AUTO_INCREMENT counter tableEamon Daly24 Aug
      • Re: MyISAM vs. InnoDB for an AUTO_INCREMENT counter tableSGreen24 Aug
  • Re: MyISAM vs. InnoDB for an AUTO_INCREMENT counter tableGleb Paharenko24 Aug
  • Re: MyISAM vs. InnoDB for an AUTO_INCREMENT counter tableDaniel Kasak25 Aug