I'm surprised it took somebody so long to pick up on this one. If you really crank up the logging you spend a whole hell of a lot more time blocking (waiting to the syscall to transfer the information) than you do running!
Drew Northup, N1XIM > -----Original Message----- > From: Mikhail Ramendik [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 26, 2004 4:34 PM > To: DBMAIL Developers Mailinglist > Cc: dbmail@dbmail.org > Subject: [Dbmail-dev] _ic_fetch() slow because of syslog (!!!) We need a > logof our own > > > Hello, > > I have found the culprit that makes fetching slow. > > Unbelievable, but it's none other than the syslog calls in trace() ! > > When I hacked it to have syslog off and verbosity to stderr on (the -v > switch does not work for some reason), and just redirected stderr to a > file, I got over 180 messages per second ! (With both of my patches - I > think they're still needed). > > Therefore I'm writing to tell users that the workaround is to lower the > TRACE_LEVEL as low as you can live with. > > And, to tell developers that we probably need a log file of our own. I'm > unable to implement it as I am not familiar enough with the C library, > and with the code (to understand where the file should be opened and > closed), and with working with files from forked processes. > > This is a MAJOR speed issue. I think it's a blocker for 2.0.1. > > Yours, Mikhail Ramendik > > > > >
