Am 24.10.2008 um 16:07 schrieb Giulio Ferro:
Daniel Urstöger wrote:
Here is the funny thing:
select messageblk_idnr from dbmail_messageblks where
physmessage_id=xxx order by messageblk_idnr;
==> takes about 0.05 sec
SELECT messageblk, is_header FROM dbmail_messageblks WHERE
physmessage_id = xxx ORDER BY messageblk_idnr;
==> takes about 4 minutes
SELECT messageblk, is_header FROM dbmail_messageblks WHERE
physmessage_id = xxx;
==> takes about 0.10 sec
Well that is certainly odd, that the ordering adds that much time.
Anyhow, I ran the
querries on my 10GB database of dbmail and it does take less then
0,05 seconds.
My dbmail db is about 18.5 GB.
I think you should try to increase your innodb_buffer_pool within
your mysql config.
I've set innodb_buffer_pool_size to 1500M and the db creates 3 files
of that
size. I can't have them any bigger because the system complains that
there is a 4 GB limit, even though the system is full 64 (and I've
compiled mysql
on it)
You can also check mysql.com for "database tuning", they have a few
guides and some
nice web cast on that topic, including stuff from Jay Pipes, just
Google the name, you will find
it for sure. Also mysql performance blog is a good point to start,
and focus on the innodb
related parameters.
I'll try that...
Also if you post your hardware configuration and the my.cnf here
somebody might have a
hint for you.
Ok, here it is:
Well, seems like I have been wrong, as Paul pointed out the selected
rows are
way to many, so there seems to be something wrong within the database.
I just checked
for myself and on my explains there are usually from 2 to well 10 rows
but
not 2 000 000.
Greetings,
Daniel_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
