From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 20:14:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 227A416A4CE for ; Sun, 11 Jul 2004 20:14:42 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id B729B43D4C for ; Sun, 11 Jul 2004 20:14:41 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i6BKEdmb018714; Sun, 11 Jul 2004 15:14:39 -0500 (CDT) (envelope-from dan) Date: Sun, 11 Jul 2004 15:14:39 -0500 From: Dan Nelson To: asfdqwer xzcvdsf Message-ID: <20040711201439.GC95931@dan.emsphone.com> References: <20040710181232.95705.qmail@web21327.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040710181232.95705.qmail@web21327.mail.yahoo.com> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: current/perl/spamassassin X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 20:14:42 -0000 In the last episode (Jul 10), asfdqwer xzcvdsf said: > Spamassassin seems to be using a HUDGE amount of memory while just > sitting idle. On other boxes it uses about a 1/4 of the amount of > ram. Is this something I should ask in the spamassassin mailing > lists or is this the right place? > athlon1# ps axuww | grep spam > root 34350 0.0 1.2 26140 25700 ?? Is 6:43PM 0:00.87 /usr/local/bin/spamd -a -c -d -r /var/run/spamd.pid (perl5.8.4) 26MB looks about right to me. Spamassassin uses around the same amount of memory on all my systems (FreeBSD, Linux, perl 5.6, perl 5.8). It's perl, has over 400 regexes, and may be caching a bayes database. -- Dan Nelson dnelson@allantgroup.com