GeronBook/Ch3/datasets/spam/easy_ham/01702.3a7add5306fcbf4ac7eb4...

31 lines
1.2 KiB
Plaintext

Return-Path: neale@woozle.org
Delivery-Date: Sat Sep 7 06:48:17 2002
From: neale@woozle.org (Neale Pickett)
Date: 06 Sep 2002 22:48:17 -0700
Subject: [Spambayes] Ditching WordInfo
In-Reply-To: <200209070533.g875XN813509@pcp02138704pcs.reston01.va.comcast.net>
References: <LNBBLJKPBEHFEDALKOLCOEKKBCAB.tim.one@comcast.net>
<w53n0qubcpj.fsf@woozle.org>
<200209070533.g875XN813509@pcp02138704pcs.reston01.va.comcast.net>
Message-ID: <w537khybba6.fsf@woozle.org>
So then, Guido van Rossum <guido@python.org> is all like:
> Maybe. I batch messages using fetchmail (don't ask why), and adding
> .4 seconds per message for a batch of 50 (not untypical) feels like a
> real wait to me...
Yeesh. Sounds like what you need is something to kick up once and score
an entire mailbox.
Wait a second... So *that's* why you wanted -u.
If you can spare the memory, you might get better performance in this
case using the pickle store, since it only has to go to disk once (but
boy, does it ever go to disk!) I can't think of anything obvious to
speed things up once it's all loaded into memory, though. That's
profiler territory, and profiling is exactly the kind of optimization
I just said I wasn't going to do :)
Neale