Re: Help! Inserts way too slow in big db

From: Steve Rapaport <[EMAIL PROTECTED]> > CREATE TABLE White ( Your table definition isn't exactly acurate, it's missing some column declorations and things. But that's OK, I didn't really need to see it created. Maybe I can offer some programatic help instead of DB design or MySQL help. I no

Re: Help! Inserts way too slow in big db

A good thought, in fact it's mentioned in my original post. My problem with that is that at the current table size, an index can take more than 24 hours to generate when the table is full, and I can't find any way to measure its progress. So I won't know if I'm waiting for days for something, or

Re: Help! Inserts way too slow in big db

VALinux 2-CPU P3, 800 Mhz, using mysql Ver 11.15 Distrib 3.23.37, for pc-linux-gnu (i686) Tables are MyISAM. Computer has 1 GB of memory, tuned for large DBs. Philip Molter wrote: >On Thu, Dec 20, 2001 at 08:32:55PM +0100, Steve Rapaport wrote: >: Okay, here's a tuning/opt problem for you

Re: Help! Inserts way too slow in big db

On Thu, Dec 20, 2001 at 08:32:55PM +0100, Steve Rapaport wrote: : Okay, here's a tuning/opt problem for you experts: : : I have several CD's worth of records that are being converted : and then inserted into our phone listing database. the total : db size will be about 22 million listings. What

Re: Help! Inserts way too slow in big db

One thing to keep in mind when using LOAD is to be sure when you telnet to "cd" to the directory where the file is that you want to load, and then get into mysql and do the LOAD statement. It's a simple thing to overlook, and if you don't do this it won't work. John McConnell -- --

Re: Help! Inserts way too slow in big db

So let's say I were to change my convert&load program to write a batch of records to a local file, then call LOAD INTO to load it. Obviously this adds some extra disk overhead, but if LOAD INTO is fast enough, maybe it's worth it. What would be a good size / number of records for such a batch?

Re: Help! Inserts way too slow in big db

> I have several CD's worth of records that are being converted > and then inserted into our phone listing database. the total > db size will be about 22 million listings. Take a look at the LOAD INTO command, it was designed specifically for mass INSERTs and is well optimized for the procedure.