Re: Insert problems with InnoDB (big table)

2004-08-06 Thread Luc Charland
Harrison wrote: Hi, sorry about the long delay in the reply. I will be away for the next 2 weeks, but I will follow this thread if anything new comes up. Hi, A few more ideas you can try: 1. SET UNIQUE_CHECKS=0; You have a unique key that is quite large (model, id name). If you know the

Re: Insert problems with InnoDB (big table)

2004-08-05 Thread Luc Charland
[EMAIL PROTECTED] wrote: Are you disabling autocommit before doing the inserts? And committing after all inserts are complete? We tried commiting every 1000, 1, 10 and 100 records. We basically have the same results. I will try to see if commiting after 10 million inserts does

Re: Insert problems with InnoDB (big table)

2004-08-05 Thread Luc Charland
Hi Frank, you actually got me doubting here. We don't use mysql client, but I made sure that autocommit was turned off. I double checked (with select count(*) from smalltest) to see the inserts were in fact commited by chunk of 100,000 and not one by one, and it was. We still see exactly the

Re: Insert problems with InnoDB (big table)

2004-08-05 Thread Luc Charland
[EMAIL PROTECTED] wrote: Estimado Luc, Con fecha jueves 5 de agosto de 2004, 11.07.23, escribió: Did you try disable index table? When you import millon of records there is an overload indexing it. First import and then create your index or: ALTER TABLE tb_name DISABLE KEYS; import data...

Re: Insert problems with InnoDB (big table)

2004-08-05 Thread Harrison
Hi, A few more ideas you can try: 1. SET UNIQUE_CHECKS=0; You have a unique key that is quite large (model, id name). If you know the data is already unique (ie. importing from another data source), then this can speed up the import *a lot*. 2. SET FOREIGN_KEY_CHECKS=0; You didn't mention

Re: Insert problems with InnoDB (big table)

2004-08-04 Thread Dr. Frank Ullrich
Luc, do you use the mysql client for the insert operations? And is autocommit set to yes? Then the answer is: turn off autocommit mode and commit every high number but not too high to grow InnoDB's transaction handling resources too big rows. Commit every 100,000 rows for example. The speeds up

RE: Insert problems with InnoDB (big table)

2004-08-04 Thread Amit_Wadhwa
Are you disabling autocommit before doing the inserts? And committing after all inserts are complete? -Original Message- From: Luc Charland [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 03, 2004 7:54 PM To: [EMAIL PROTECTED] Subject: Insert problems with InnoDB (big table) We are

Re: Insert problems with InnoDB (big table)

2004-08-04 Thread David Griffiths
Also, are the indexes in place when you start your inserts? Constantly updating those indexes will be slow; try inserting without indexes, and then building the indexes. You can also limit the size of your index file by, 1) Making sure all columns are as small as possible (ie MEDIUMINT rather