Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (athena.apache.org: domain of cctrieloff@redhat.com
 designates 66.187.237.31 as permitted sender)
Message-ID: <498C3B16.4010203@redhat.com>
Date: Fri, 06 Feb 2009 08:28:54 -0500
From: Carl Trieloff <cctrieloff@redhat.com>
Reply-To: cctrieloff@redhat.com
Organization: Red Hat
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: users@qpid.apache.org
Subject: Re: About footprint size
References: <1233898402793-2279278.post@n2.nabble.com>
In-Reply-To: <1233898402793-2279278.post@n2.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

chenta wrote:
> Hi,
> I am curious about the footprint size of C++ client and broker. I can not
> find the related info from the documents.
> After I calculate the total object size of qpid/src/clinet and broker, the
> total size is about 21 MB and 40 MB. Is it the right way/answer for this
> question? 
>
> B.R.
> Chenta
>   

For the broker, the memory footprint is determined more by your queue 
depth. The max size for the
broker can be managed by using an external store and the flow-to-disk 
policies capping the max bytes
allowed per queue, or size of messages before flowing the data to disk.

So the short answer is, depends on how you wish to manage queue depth.

Client will always be small, unless you increase the amount the client 
may buffer, by increasing the bound-multipler
property. This controls how many frames the client may buffer before 
blocking the client user thread.

Carl.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org