On Tue, 13 May 2008, [EMAIL PROTECTED] wrote:
We've been testing DBMail for a few months now and did a test launch
yesterday. We have about 850 pop3/imap users accessing through the webmail,
Outlook and mobile devices. Things were fine when we tested with a few users,
but after we put it in production - we get about a hundred concurrent
connections - MySQL just grinds to a halt. I've tweaked so many settings but
nothing helped. I think the problem might be because the DBMail database
isn't indexed properly or has no indexing at all... I haven't verified yet.
My question is: does the schema that comes with DBMail already have indexing
defined in it or do I have to do my own indexing and optimization?
There are some indices. Whether there are indices for every query that the
system could throw at the DB, I don't know.
You could, of course, apply the slow-query-log, and get it to also log all
queries that run unindexed.
The chances are that checking this would have taken less time than appling DB
engine tweaks and typing up the email. :^)
Is the problem CPU or I/O bound?
Our server is a dual 64bit xeon with 4GB of RAM on a RAID1 SCSI
FreeBSD 7
MySQL 5.1
Some one on this list mentioned that they run DBMail with 5000 users no
problem so I'm wondering why ours crawed to a stop.
If you are seeing lots of connections, it sounds like something is running
unindexed. Get the slow/unindexed query logging going and take it from there.
850 users, even heavy ones, shouldn't be a problem on the sort of hardware you
have.
Gordan
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
