sql,query
At 15:50 -0600 10/25/02, Jeff Mathis wrote:
Paul DuBois wrote:
>(2) drop all indexes on your table(s). rebuild them after loading (this
>alone can give orders of magnitude improvement)
For ISAM or MyISAM, that works. It has no effect for InnoDB.
Do you actually observe a rep
In the last episode (Oct 25), Jeff Mathis said:
> I'll agree to this somewhat:
>
> (1) always bind your variables. whatever code you are using to do your
> inserts, the fewer prepared statements you can make the better.
>
> for example:
> insert into TableName (col1, col2, col2, col4) values (?,?
David Lloyd wrote:
Mark,
Note that mysql does not support bind variables. If you think
you're>using them, whatever API you are using is filling them in
before>sending the statement to mysql. Bind variables do solve
quoting>problems, though, so if you use them, know why you're using
them :)>
At 15:46 -0600 10/25/02, Jeff Mathis wrote:
forgive me.
i was initially using the perl DBI methods to load. I am not intimately
familiar with the inner workings of DBI, but obviously it must be doing
something if you say mysql does not support binding variables
(i am using 4.0.4). This is signifi
Mark,
> >>Note that mysql does not support bind variables. If you think
> >you're>using them, whatever API you are using is filling them in
> >before>sending the statement to mysql. Bind variables do solve
> >quoting>problems, though, so if you use them, know why you're using
> >them :)>
Rumou
Jeff Mathis wrote:
forgive me.
i was initially using the perl DBI methods to load. I am not intimately
familiar with the inner workings of DBI, but obviously it must be doing
something if you say mysql does not support binding variables
(i am using 4.0.4). This is significantly faster than creati
forgive me.
i was initially using the perl DBI methods to load. I am not intimately
familiar with the inner workings of DBI, but obviously it must be doing
something if you say mysql does not support binding variables
(i am using 4.0.4). This is significantly faster than creating a new
prepared st
Jeroen Geusebroek wrote:
[snip]
You where right, what i did use indivudual inserts. Now I have it
segmented in 1000 rows in one query which massively speeds up the whole
inserting progress. 160K records now takes about 20 seconds instead of
the 100 records ;) I'm really impressed by this massive s
_field2),(?,?),(?,?) etc etc
>
> Ric.
>
> - Original Message -
> From: "Jeroen Geusebroek" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, October 25, 2002 12:11 PM
> Subject: Mysql Innodb performance slow
>
> Hi There,
>
> We ha
why the isam table takes about 100
seconds for inserting 160K rows, while innodb takes 700 seconds. (using
individual inserts)
Thanks,
Jeroen
> -Original Message-
> From: Jeroen Geusebroek [mailto:j.geusebroek@;infraxs.com]
> Sent: Friday, October 25, 2002 3:11 AM
> To
ginal Message -
From: "Jeroen Geusebroek" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 25, 2002 12:11 PM
Subject: Mysql Innodb performance slow
Hi There,
We have currently an Interbase Database with millions and millions of
rows which I would
Hi There,
We have currently an Interbase Database with millions and millions of
rows which I would like
to migrate to MySQL if possible to increase the speed.
Transaction support is necessary, so I am using innoDB.
When inserting 160K rows in the database (in an innoDB table) it takes
about 700
12 matches
Mail list logo
