anomy-list

Re: Re: 100 % CPU utilization Postfix+Anomy+SpamAssassin+ClamAV

From: Paolo (139740@xyz.molar.is)
Date: Wed 09 Feb 2005 - 10:32:37 GMT

  • Next message: Bjarni R. Einarsson: "Daemonized sanitizer?"

    On Tue, Feb 08, 2005 at 07:57:11PM -0500, Derrick Webber wrote:
    > Paolo wrote:
    > > On Tue, Feb 08, 2005 at 11:26:55AM -0800, Peter Mueller wrote:
    > >
    > >># perlcc sanitizer.pl -o sanitizer
    > >>/tmp/ccZDnQzM.o: In function `dl_init':
    > >>/tmp/ccZDnQzM.o(.text+0x114da8): undefined reference to `boot_MIME__Base64'
    > >>/tmp/ccZDnQzM.o(.text+0x114e5e): undefined reference to `boot_Digest__MD5'
    > >>collect2: ld returned 1 exit status
    > >
    ...
    > > and got a ~7MB sanitizer.c (!)
    ...
    > and processing time per message. You can reduce the size of the binary
    > a little using "strip".

    eh, note I didn't get a binary to strip, yet ;)

    > I have several sparc solaris 8 systems using sanitizer.pl compiled
    > with perl 5.8.0 and it works flawlessly.

    great... let me find a 'Sarge' installation to try then.

    > What's really needed to reduce sanitizer's overhead is a daemonized
    > version (how about it, Bjarni? ;-). Once perl gets running it's very

    yes, like clamd; but sanitizer may call a number of helpers which may
    slow things down as well.

    > fast but the startup overhead is a killer. Short of rewriting the
    > sanitizer as a daemon, Persistent Perl
    > (http://daemoninc.com/PersistentPerl/) seems to work. It's originally

    so, what's your numbers with .pl, perlcc'd, perperl cases?

    -- 
     paolo
     
     GPG/PGP id:0x21426690 kfp:EDFB 0103 A8D8 4180 8AB5  D59E 9771 0F28 2142 6690
     "Indeed, it does come with warranty: it *will* fail, sometimes, somehow..."
                                                               - software vendor
    



    hosted by molar.is