Return-Path: Delivered-To: apmail-gump-general-archive@www.apache.org Received: (qmail 73621 invoked from network); 5 Mar 2004 23:37:40 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 5 Mar 2004 23:37:40 -0000 Received: (qmail 55538 invoked by uid 500); 5 Mar 2004 23:37:26 -0000 Delivered-To: apmail-gump-general-archive@gump.apache.org Received: (qmail 55511 invoked by uid 500); 5 Mar 2004 23:37:25 -0000 Mailing-List: contact general-help@gump.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Gump code and data" Reply-To: "Gump code and data" Delivered-To: mailing list general@gump.apache.org Received: (qmail 55497 invoked from network); 5 Mar 2004 23:37:25 -0000 Received: from unknown (HELO mx1.try.sybase.com) (130.214.10.19) by daedalus.apache.org with SMTP; 5 Mar 2004 23:37:25 -0000 Received: from mail.try.sybase.com (mail.try.sybase.com [130.214.10.18]) by mx1.try.sybase.com (8.11.6/8.11.0) with ESMTP id i25MZ8205057 for ; Fri, 5 Mar 2004 15:35:08 -0700 Received: from tsws1 ([10.22.120.107]) by mail.try.sybase.com (8.11.6/8.11.6) with SMTP id i25NJhk30195 for ; Fri, 5 Mar 2004 16:19:44 -0700 Message-ID: <0b7b01c4030a$ce51cc40$d88b1f43@tsws1> From: "Adam R. B. Jack" To: "Gump code and data" References: Subject: Re: gumpy memory size Date: Fri, 5 Mar 2004 16:37:13 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I'm watching a Gumpy run, and it's memory usage is minute in comparison: 18013 ajack 16 0 24116 5324 1028 S 1.3 0.5 3:20 0 python > last night's run is still running (that's about 14 hours). Memory > usage...454mb: > 1642 ajack 30 15 454M 201M 154M R N 1.5 80.7 34:08 0 python > do we have a memory leak somewhere? Could it be that Gumpy was niced so low that Python's garbage collection loop (I assume it has one) wasn't kicking in? Long shot, but I wonder. For anybody whose looked at the logs a little while back, you'd've seen I tried to detect resources (via Python call) but it doesn't appear to be fully implemented & reports '0' for memory usage. Anyways, memory usage doesn't seem to be a problem right now. BTW: I did put a lock into gumpy.py, not that this is finished/fully deployed yet. regards, Adam --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@gump.apache.org For additional commands, e-mail: general-help@gump.apache.org