On Sat, 21 Jul 2001, Sergei Golubchik wrote:
> Date: Sat, 21 Jul 2001 10:36:22 +0200
> From: Sergei Golubchik <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: Tom Wheeler <[EMAIL PROTECTED]>
> Subject: Re: Questions about extremely large database support
>
> Hi!
>
> On Jul 20, Jeremy Zawodny wrote:
> > On Thu, Jul 19, 2001 at 03:15:02PM -0500, Tom Wheeler wrote:
> > >
> > > Our two most important requirements for the database engine are
> > > speed and scalability. We will be inserting probably 5,000,000
> > > records per day into our database
> >
> > Sounds doable--on reasonable hardware.
> >
>
> Well, on my tests I was able to add ~4,000,000 rows in 17 hrs
> with MySQL 3.23, and in 4 hrs in MySQL 4.0
>
> Table had 4 indexes. Removing those increased the speed by
> several orders of magnitude (!!!).
>
> Hadware was moderate - Athlon 1GHz, 640M RAM.
>
> Regards,
> Sergei
>
Ok, how long did it take afterwards to alter table and put the extra
indexes back? Isn't there a flag which allows the insert to ignore
errors (ie., duplicate unique fields). If this is true, couldn't the
insert be programmed to do the insert and then add the indexes after ALL
the inerts were loaded? Some kind of bulk load syntax? Just a thought?
Sincerely,
William Mussatto, Senior Systems Engineer
CyberStrategies, Inc
ph. 909-920-9154 ext. 27
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
