Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 14100 invoked from network); 14 Oct 2010 17:27:48 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 14 Oct 2010 17:27:48 -0000 Received: (qmail 12019 invoked by uid 500); 14 Oct 2010 17:27:47 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 12001 invoked by uid 500); 14 Oct 2010 17:27:47 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 11993 invoked by uid 99); 14 Oct 2010 17:27:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Oct 2010 17:27:47 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=10.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cctrieloff@redhat.com designates 209.132.183.28 as permitted sender) Received: from [209.132.183.28] (HELO mx1.redhat.com) (209.132.183.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Oct 2010 17:27:43 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o9EHRLTi019204 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 14 Oct 2010 13:27:22 -0400 Received: from [10.16.19.120] (dhcp-100-19-120.bos.redhat.com [10.16.19.120]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o9EHRLnY007694 for ; Thu, 14 Oct 2010 13:27:21 -0400 Message-ID: <4CB73D74.201@redhat.com> Date: Thu, 14 Oct 2010 13:27:16 -0400 From: Carl Trieloff Reply-To: cctrieloff@redhat.com Organization: Red Hat User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-3.fc13 Thunderbird/3.0.4 MIME-Version: 1.0 To: users@qpid.apache.org Subject: Re: queue memory release References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 10.5.11.12 On 10/14/2010 12:50 PM, Adam Crain wrote: > I am writing the list again to ask about when qpid releases memory from queues that become bloated and are subsequently read. > > I got a response from Carl a while back who suggested the OS is the culprit and not qpid: > > http://mail-archives.apache.org/mod_mbox/qpid-users/201010.mbox/%3C4CAE3792.8080100@redhat.com%3E > > This explanation doesn't seem to agree with simple a cpp test program I've posted: > > http://gist.github.com/454032 > > Can someone explain in more detail why Qpid's memory usage might differ from a simple C++ example that news/deletes memory? > > thanks, > Adam > > It is released once the message has been accepted from all the queues it is enqueued on. take a look at the queues with qpid-tool. if they are gone, close qpidtool and the mem is released. if the process is still blotted that is linux lazy release. These can be seen from when tc_consolidate is being called. Carl. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org