SVN should be stable at this time, though we have a few bugs outstanding that have not been completely identified and resolved. Your mileage may vary.
But that's sort of beside the point -- pegging the cpu at 100% for 2 seconds upon each message delivery is not a "performance issue," it's a disaster! Something on Eric's machine is not right, and hopefully we'll be able to help identify and resolve the issue with him. Aaron On Wed, Apr 4, 2007, Jesse Norell <[EMAIL PROTECTED]> said: > There have been some changes to improve speed since 2.2.2 though, > haven't there? From irc conversation, another pertinent question is, is > 2.2 svn stable right now? I know there were a run of issues a week or > two back, but have the major issues cleared? If so, Eric could probably > try latest svn and report back on speed differences. > > Jesse > > > On Wed, 2007-04-04 at 20:33 +0000, Aaron Stone wrote: >> That's not DBMail being slow, it's your database. Run top during message >> delivery and you'll see who's eating the cpu. Most likely you need to >> vacuum/optimize/analyze your tables. dbmail-util -c will do this for you. >> >> Aaron >> >> On Wed, Apr 4, 2007, Eric Hiller <[EMAIL PROTECTED]> said: >> >> > I have been running 2.2.2 and it has been very stable. Ran it as soon as >> > it >> > came out and it worked on a test machine. Only thing is it is MUCH slower >> > than 2.0.10. Any mail request and the sql server cpu is pegged at 100% for >> > 2+ seconds. Is this issue resolved, or will it be in 2.2.5? >> > >> > Thanks much for dbmail it really has been great, >> > Eric > > -- > Jesse Norell - [EMAIL PROTECTED] > Kentec Communications, Inc. > > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
