Goran, actually I was one of the few cases where going to the persistent sniffer was detrimental.
The cause was lack of hardware. My server was already running at 100% cpu and with busy disks all too much, and I thought that going to persistent mode would lighten the load enough to make more room for Declude. Instead, I saw timeouts that showed Declude waited it's maximum time without Message Sniffer returning. It was actually the other way around, though. I concluded that 1) Declude logging in debug mode shows that Declude boosts it's CPU priority, and that this starved out Sniffer. 2) that my cpu problems masked my seriously underperforming SCSI2 mirror. The right honourable R. Scott Perry heeded my request to modify the Declude log technique (old technique: write to disk every line as soon as it can, which led to busy disks, interleaved logs per message, and screwed up overlapping log lines; new technique: batch all log lines until processing is done, then write all of them at one go) and at the same time brought in "shortcircuit grammar" like SKIPIFWEIGHT. I also clued in that I should be rotating my Message Sniffer log at least daily, and ideally to upload them to SortMonster/ARM to feed back into the system. With all of those changes, my disk time quieted down enough and my extensive Declude filters quieted down enough that Message Sniffer ran *great* in the persistent mode, and I ran in that configuration long enough to upgrade the hardware at my convenience. By all means, try it. All it takes to test it is launching as Pete mentioned in this thread. You can always implement the srvany.exe technique or FireDaemon later. I use FireDaemon. To save yourself some typing and remembering, you can use the sample batch files that Message Sniffer includes, e.g. send-start.cmd but remember to edit the .exe file they reference so that is the same name as your licenceid.exe file. The observed behaviour of a well-functioning Message Sniffer is that in Task Manager, you will see one licenceid.exe that uses small bursts of CPU time, and then zero or more other licenceid.exe which come and go (the PID column changes). Andrew 8) > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Goran Jovanovic > Sent: Thursday, February 23, 2006 8:47 AM > To: sniffer@SortMonster.com > Subject: RE: [sniffer] When to go persistent > > Andrew, > > So when you went to persistent it lowered the stress on your > already stressed hardware? > > And I see that Pete has responded as I write this with: "Use it" > > Well I will set it up and see how my system reacts. > > Goran Jovanovic > Omega Network Solutions > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > On Behalf Of Colbeck, Andrew > > Sent: Thursday, February 23, 2006 11:39 AM > > To: sniffer@SortMonster.com > > Subject: RE: [sniffer] When to go persistent > > > > Goran, I'd be interested in Pete's technical answer, too. > > > > The practical answer is that you should always go with the > persistent > > instance of Message Sniffer. From reading Pete's previous > screeds and > > monitoring the list here in the last year and from having my own > > troubles, it's pretty clear to me that only marginal cases > suffer with > > the persistent mode (and I was one of them). > > > > Pete's answer on volumes won't answer what are the marginal > cases, it > > just doesn't fit your question. For me, it was simple lack of > hardware, > > but I was *right* on the edge. > > > > Andrew 8) > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On Behalf Of Goran > Jovanovic > > > Sent: Thursday, February 23, 2006 8:30 AM > > > To: sniffer@SortMonster.com > > > Subject: [sniffer] When to go persistent > > > > > > Hi, > > > > > > Is there any good rule of thumb, in terms of messages > processed per > > > minute/hour/day when you should move to a persistent instance of > > > Sniffer? > > > > > > Thank you > > > > > > Goran Jovanovic > > > Omega Network Solutions > > > > > > > > > This E-Mail came from the Message Sniffer mailing list. For > > > information and (un)subscription instructions go to > > > http://www.sortmonster.com/MessageSniffer/Help/Help.html > > > > > > > > > This E-Mail came from the Message Sniffer mailing list. For > information > > and (un)subscription instructions go to > > http://www.sortmonster.com/MessageSniffer/Help/Help.html > > > This E-Mail came from the Message Sniffer mailing list. For > information and (un)subscription instructions go to > http://www.sortmonster.com/MessageSniffer/Help/Help.html > This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
