On 31-05-14 16:35, Daniel Schütze wrote: > I've had this issue before and on occasion is raises its head and it tends > to disappear but Friday was extremely bad and it's not showing signs of > abating.
> What I've noticed this time is that after restarting there is a build up of > threads in mysql reporting state null and info commit. (thread# are low as > in desperation I restarted mysql last night). sucks. > |5649|dbmail|localhost|dbmail|Query|0||COMMIT| All the IDLE times on the COMMIT lines are very low (0|1), so it's not something hanging inside mysql. > > Does anyone have any ideas what might be causing this and how to avoid it? > > The server is FreeBSD 8.1, mysql 5.1.x. My dbmail.conf max_db_connections > = 35 but I've tried 10 and 20 too to no avail. 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. Are you planning on upgrading mysql? 5.1 is quite old, and 5.5 is known to be significantly faster. 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! > > Regards > > Daniel Schütze > > > _______________________________________________ > DBmail mailing list > [email protected] > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail > -- ________________________________________________________________ Paul J Stevens pjstevns @ gmail, twitter, github, linkedin www.nfg.nl/[email protected]/+31.85.877.99.97 _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
