>What kind of concurrency pressure are you dealing with (number of >concurrent connections at peak moments). Even 10 seems high-ish, but 20
>or larger is way too high for max_db_connections. Sorry, do you mean how many clients will have an active connection open? We have about 100 users and of those perhaps 20 will have a desktop client connected via idle so their connections are open constantly; then another 20 or so will use such clients on a more limited basis. I guess on top of that we have circa 30 people with frequent or constant access on mobile devices. Does dbmail allow on reporting the concurrent connections? >Are you planning on upgrading mysql? 5.1 is quite old, and 5.5 is known >to be significantly faster. We have MySQL5.5 on the server "to be" (currently mysql slave and also accepting some imap connections which go back to the production server over network mysql connection) which is meant to be replacing the production server but we still haven't gotten round to it. We'll have to update 5.1 to 5.5 when the production becomes a slave but I'm very hesitant of doing it before incase anything goes wrong! >It might be the usage pattern you're dealing with. Webmail clients tend >to do massive amounts of connects/disconnects. Using imapproxy will help >bring those down a lot! We do offer squirrel/roundcube access but it's a limited number of users who access this at the same time (I don't recall more than 5 at once). Regards Daniel
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
