Theo Van Dinter wrote: > On Wed, Jan 30, 2008 at 01:11:53PM -0500, Matt Kettler wrote: >> You can try it if you like. The existing rules are the result of some >> testing >> that was done several years ago. I think it was Theo that did it.. > > Yeah, I wrote the rules + code way back when... I've been trying to find some > stats for this stuff, but didn't come up with anything useful. > > My recollection was that w/ e8 the cf was either really low or really high, > and we just took the 51_100 values from the older pre-e8 rules and made it all > consistent. > > I don't recall e4 stats. > >> I just re-tweaked my Core.pm to make cf comparison logging a lower-level >> event >> so I can check if this has changed. So far (only a minute or two) I've >> gotten 5 >> e8's and 1 e4, all cf=100. > > Yeah, unfortunately we don't log the actual cf values anywhere by default, so > it's hard to runs some stats w/out rerunning all messages and pounding on the > razor servers.
If you want some quick stats, I can post you a patch to Razor2's Core.pm that enables logging of cf levels in your razor-agent.log without flooding you. That's probably not useful for mass-checks, but can be useful for a little grep-based statistics gathering. By default, if you set your debuglevel=6 it will log which engines matched, at what cf level, and what signature hash. However, there's a lot of other junk that's completely uninteresting to anyone outside the razor team (ie: byte counts on a per-read/write basis come in at debuglevel=4) The patch I made moves the byte counts up to level 5, and the engine match lines down the level 4. But some quick stats for the past hour and 15 mins: e8 - 140 matches, 16 of which were less than cf 100 (11.4% of hits). e4 - 92 matches, 12 of which were less than cf 100 (13.0% of hits). Admittedly the sample is small, but you do get the idea. There is a pretty strong gravitation towards 100, so differentiating between 51-95 and 95-100 isn't much different than 51-100. > We have the NetCache plugin which was an initial attempt I was working on to > grab all network-related test results and store them in an X-Spam-* header for > later use via the --reuse option, but a) Razor2 is the only thing in there, > and b) no one enables it by default since nothing actually uses the resulting > header. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Razor-users mailing list Razor-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/razor-users