If I can't read the output, what's the point?!?! ;-) The only time it really gets wild is when a maillist goes out and it whips by pretty good, but I'm able to see any -82, -40 messages, which alerts me to either look back on the command window or open XQM.
Would a good rule of thumb be to keep it in debug mode until I'm unsatisfied with the performance? Then I can decide if I want to change the XMail mode or buy faster hardware. ;-) Thanks! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Saturday, November 04, 2006 16:58 To: [email protected] Subject: [xmail] Re: Simple performance question... On Sat, 4 Nov 2006, Norbert Doeberlein wrote: > OS: W2K3 HW: FAST > > Would there be a noticeable performance hit if you continually ran XMail > in debug mode in a command window vs. running as a service? Maybe it's > just me, but I like being able to RDP in and take a quick look to see if > something is happening instead of pulling up a lot of logs. Seeing the > verbose transactions usually gives me the first clue that something is > wrong. How many lines per second on average are printed on the console? Unless it's so bad that you can't read the output, you should be fine. - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
