From: Almar van Pel
After some time (sometimes a week sometimes a month) it appears that the
index of the table gets stuck.
It tries to read from the table but does not get response. This causes the
connectionqueue to fill up
and the load on the system increases dramatically. In other words,
or
not of internal temporary tables, ...
Mathias
-Original Message-
From: Jigal van Hemert [mailto:[EMAIL PROTECTED]
Sent: dimanche 24 avril 2005 17:05
To: Almar van Pel; mysql@lists.mysql.com
Subject: Re: Performance issues when deleting and reading on large table
From: Almar van Pel
Hi Jigal, Mathias,
Thanks the time you took to reply to my issue's!
I would like to clear out some things.
It's a probably a case of not having the cardinality of indexes right and
thus making wrong decisions for queries.
- Currently there is not a single query in the application that does
@lists.mysql.com
Cc: 'Jigal van Hemert'; 'mathias fatene'
Subject: RE: Performance issues when deleting and reading on large table
Hi Jigal, Mathias,
Thanks the time you took to reply to my issue's!
I would like to clear out some things.
It's a probably a case of not having the cardinality
It's a probably a case of not having the cardinality of indexes right
and
thus making wrong decisions for queries.
- Currently there is not a single query in the application that does not
use
the correct index. We only have key-reads. Wich would mean that MySQL is
creating these incorrect
when deleting and reading on large table
It's a probably a case of not having the cardinality of indexes
right
and
thus making wrong decisions for queries.
- Currently there is not a single query in the application that does
not
use
the correct index. We only have key-reads. Wich would mean
