"top"
Network checks are costly for time. Ping times can give useful hints.
Some rule sets are extraordinarily costly for memory and time. (There
is an "evil" rule set that's reasonable and another that is obsolete,
overgrown, and a huge system drain. Be careful to pick the right one.
Read the d
On Wed, Jul 26, 2006 at 08:38:31PM +0530, Dhawal Doshy wrote:
> >How do I know what percentage of time is taken by individual tests ?
You can't really, without profiling the perl directly.
> As Chris mentioned.. network tests (especially razor/pyzor) could be
> responsible for SA delay. If you
Ramprasad wrote:
I can tell you right now, its either Net tests or poorly written
rules. Otherwise SA runs pretty darn good.
Darn good is how good ?
On a Dual Xeon with 4GB ram can SA scan 30k mails per hour.
Today at 15k the machine starts signalling problems , 20k is the max it
can do bey
> I can tell you right now, its either Net tests or poorly written
> rules. Otherwise SA runs pretty darn good.
>
Darn good is how good ?
On a Dual Xeon with 4GB ram can SA scan 30k mails per hour.
Today at 15k the machine starts signalling problems , 20k is the max it
can do beyond which the
Title: RE: bottleneck analsyis on spamassassin
> -Original Message-
> From: Ramprasad [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 26, 2006 6:54 AM
> To: spamassassin-users
> Subject: bottleneck analsyis on spamassassin
>
>
> Hi,
> Spamassassin
