confirm it?
Thanks,
Narasimha
From: David Griffiths [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 04, 2005 10:19 PM
To: Gleb Paharenko
Cc: mysql@lists.mysql.com
Subject: Re: Slow queries, why?
Yes, indexes slow down inserts (or updates that change the value of a
column that is indexed).
Also
Hello.
There could be a lot of reasons for such a delay. First, you
should switch to bulk inserts and perform all operation as a single
transaction. Avoid usage of the autoextended or per-table tablespaces.
Are you able to upgrade? There could be some performance improvements
in the newer ve
Thanks! Explain and InnoDB monitor were exactly what I needed to
diagnose and fix the problem! In case you were curious, the issue was
that the statement I was expecting to run was not the statement that
was running, but the first hundred and some-odd characters in both
were the same. Using the mon
Yes, indexes slow down inserts (or updates that change the value of a
column that is indexed).
Also, remember that MySQL only uses one index per per table in a query.
So if there are some columns in your table that are indexed, but,
1) Have poor cardinality (number of distinct values - low card
me in this, it is very urgent.
Thanks,
Narasimha
-Original Message-
From: Gleb Paharenko [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 04, 2005 1:11 PM
To: mysql@lists.mysql.com
Subject: Re: Slow queries, why?
Hello.
> We're running MySQL 4.11 on a machine with 2GB memory, the
Hello.
> We're running MySQL 4.11 on a machine with 2GB memory, the table is
> InnoDB with a compound primary key, and additional indexes on all rows
> with searchable options in the API. Any generic advice or admin tools
> would be great.
Use EXPLAIN to determine how efficient your in
on 5/3/05 7:25 PM, Joseph Cochran at [EMAIL PROTECTED] wrote:
> So here's my situation: we have a database that has a table of about 5
> million rows. To put a new row into the table, I do an INSERT ...
> SELECT, pulling data from one row in the table to seed the data for
> the new row. When there
So here's my situation: we have a database that has a table of about 5
million rows. To put a new row into the table, I do an INSERT ...
SELECT, pulling data from one row in the table to seed the data for
the new row. When there are no active connections to the DB other than
the one making the INSE
