On Sun, 29 Dec 2002, Mike Saunders said:
> Every time you load spamassassin you have to load the entire perl
> interpreter and it's environment. It has to scan it's library pathis (I
> believe...) and you may have more in place now. That takes time. Plus
> you're running a lot of other processess as well. I would suspect this to
> be the issue at hand.
No, that is not the cause of the delay --- and there *is* an unusual delay,
compared to running smaller Perl programs.
(Working from 2.43 here):
%Time ExclSec CumulS #Calls sec/call Csec/c Name
23.6 0.449 3.354 30 0.0150 0.1118 Mail::SpamAssassin::PerMsgStatus::
BEGIN
10.5 0.200 0.575 9 0.0222 0.0639 base::import
9.99 0.190 1.470 13 0.0146 0.1131 Mail::SpamAssassin::BEGIN
IIRC, PerMsgStatus is (in 2.43) the file that includes all the tests; so
there's a massive amount of regexp parsing going on in there.
It might be nice to do this a little more lazily, so that simple things
like a -V don't take forever...
--
`I was thinking of the legendary British Weather, with the four seasons
of winter, mud, rain, and damp.' --- Peter da Silva
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
