List:General Discussion« Previous MessageNext Message »
From:Alfredo Cole Date:March 1 2005 11:24pm
Subject:Switching to InnoDB turns out dissapointing
View as plain text  
Hi:

I have switched from MyISAM tables to InnoDB, using MySQL 4.1.10 under SuSE 
8.2.

My application, an ERP system developed in-house, uses 70 tables, the largest 
one holding a little over one million rows. To assist when changing table 
structures, we developed a software that creates a new table for each of the 
70 tables, one at a time, using the new structure, copies all of the records 
from the old table to the new one, drops the old one and renames the new one.

Using MyISAM tables, this process takes 10 minutes using a two Xeon 2.4 Ghz 
server, with 4 Gb RAM and SCSI RAID 5 disks. The same system takes 2 1/2 
hours using InnoDB tables with the same configuration. We have followed the 
guidelines for tuning the server, and still, we find this to be excessive. 
Can somebody point to some docs, guidelines or web sites we can consult to 
improve InnoDB's performance? It seems inserting many rows decreases 
performance significantly.

Thank you and regards.

-- 
Alfredo J. Cole
Grupo ACyC
www.acyc.com - www.clshonduras.com - SolCom - www.acycdomains.com
Thread
Switching to InnoDB turns out dissapointingAlfredo Cole2 Mar
  • Re: Switching to InnoDB turns out dissapointingGary Richardson2 Mar
    • Re: Switching to InnoDB turns out dissapointingScott Klarenbach2 Mar
    • Re: Switching to InnoDB turns out dissapointingAlfredo Cole2 Mar
      • Re: Switching to InnoDB turns out dissapointingGary Richardson2 Mar
      • Re: Switching to InnoDB turns out dissapointingJochem van Dieten2 Mar
Re: Switching to InnoDB turns out dissapointingHeikki Tuuri2 Mar
  • Re: Switching to InnoDB turns out dissapointingAlfredo Cole2 Mar
    • Re: Switching to InnoDB turns out dissapointingBrent Baisley2 Mar
      • Re: Switching to InnoDB turns out dissapointingAlfredo Cole2 Mar
        • Re: Switching to InnoDB turns out dissapointingBrent Baisley2 Mar
          • Re: Switching to InnoDB turns out dissapointingAlfredo Cole3 Mar
          • Re: Switching to InnoDB turns out dissapointingPhilippe Poelvoorde3 Mar
RE: Switching to InnoDB turns out dissapointingJon Frisby2 Mar
Re: Switching to InnoDB turns out dissapointingHeikki Tuuri2 Mar