List:General Discussion« Previous MessageNext Message »
From:Jochem van Dieten Date:March 2 2005 12:32am
Subject:Re: Switching to InnoDB turns out dissapointing
View as plain text  
On Tue, 1 Mar 2005 18:09:37 -0600, Alfredo Cole wrote:
> El Mar 01 Mar 2005 17:32, Gary Richardson escribió:
>>
>> InnoDB uses transactions. If you are doing each row as a single
>> transaction (the default), it would probably take a lot longer.
>>
>> I assume you're doing your copying as a INSERT INTO $new_table SELECT
>> * FROM $old_table. Try wrapping that in a
>>   BEGIN;
>>   INSERT INTO $new_table SELECT * FROM $old_table;
>>   COMMIT;

> This is the InnoDB related stuff from my.cnf:
> 
> innodb_data_file_path = ibdata1:10M:autoextend
> set-variable = innodb_buffer_pool_size=192M
> set-variable = innodb_additional_mem_pool_size=32M
> set-variable = innodb_log_file_size=5M
> set-variable = innodb_log_buffer_size=32M
> innodb_flush_log_at_trx_commit=0
> set-variable = innodb_lock_wait_timeout=50
> 
> I am using the syntax as you describe it.

If the transactions you are using insert thousands of records (or
more) it is probably faster to leave the default value for
innodb_flush_log_at_trx_commit. It is recommended anyway for data
security.

Jochem
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