You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by chenta <ch...@gmail.com> on 2009/02/06 06:33:22 UTC
About footprint size
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
--
View this message in context: http://n2.nabble.com/About-footprint-size-tp2279278p2279278.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
RE: About footprint size
Posted by Steve Huston <sh...@riverace.com>.
There's an open jira for this, QPID-1625.
https://issues.apache.org/jira/browse/QPID-1625
-Steve
> -----Original Message-----
> From: chenta lee [mailto:chenta@gmail.com]
> Sent: Monday, February 09, 2009 11:37 AM
> To: users@qpid.apache.org
> Subject: Re: About footprint size
>
>
> Thanks Cliff,
> I got a windows machine and try to build C++ qpid client on
> it. But when I
> try to build the example, it always failed at "stdint.h"
> file. I have tried
> many different version of stdint.h file, likes boost/cstdint.hpp, or
> pstdint.h. But neither of them can pass.
> Could you tell me how to compile the examples on the windows
machine?
>
> On Sat, Feb 7, 2009 at 3:30 AM, Cliff Jansen (Interop Systems Inc) <
> v-cljans@microsoft.com> wrote:
>
> > In M4, the Windows C++ clients are built using static
> libraries. So each
> > client program must duplicate the needed code from the
> client libraries.
> >
> > A small program like perftest (but which pulls in much client
> > functionality) will be about 2.2Mb in size. Qpidbroker.exe
> is 1.6Mb.
> >
> > This will all change in M5 as dynamic library (DLL) support
> is being added
> > to the Windows C++ port.
> >
> > Cliff
> >
> > -----Original Message-----
> > From: chenta [mailto:chenta@gmail.com]
> > Sent: Friday, February 06, 2009 9:12 AM
> > To: users@qpid.apache.org
> > Subject: Re: About footprint size
> >
> >
> > Thank you Carl.
> >
> > I think I shouldn't use "footprint" right here. What I need
> to know is if I
> > install a c++ client on a computer, how many disk space do I need?
> > I already build the c++ client library on my linux machine.
> And I have the
> > following assumption: When using dynamice link at run time. We
need
> > libqpidclient.so and libqpidcommon.so which is about 26 MB
> large. And I
> > think sslconnector.so is needed when using SSL connection.
> Am I correct?
> >
> > What about the c++ client on windows system? I currently
> have no windows
> > machine around. Could anyone help me to figure it out?
> >
> > Thanks,
> > Chenta
> >
> >
> >
> > On Fri, Feb 6, 2009 at 9:32 PM, Carl Trieloff (via Nabble) <
> >
> ml-user+168296-1934286974@n2.nabble.com<ml-user%2B168296-19342
> 86974@n2.nabble.com>
> >
> <ml-user%2B168296-1934286974@n2.nabble.com<ml-user%252B168296-
> 1934286974@n2.nabble.com>
> > >
> > > wrote:
> >
> > > 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@...<
> >
http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2284115&i=0>
> > >
> > >
> > >
> > > ------------------------------
> > > This email is a reply to your post @
> > > http://n2.nabble.com/About-footprint-size-tp2279278p2284115.html
> > > You can reply by email or by visting the link above.
> > >
> > >
> >
> > --
> > View this message in context:
> > http://n2.nabble.com/About-footprint-size-tp2279278p2285298.html
> > Sent from the Apache Qpid users mailing list archive at
Nabble.com.
> >
> >
>
---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project: http://qpid.apache.org
> > Use/Interact: mailto:users-subscribe@qpid.apache.org
> >
> >
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: About footprint size
Posted by chenta lee <ch...@gmail.com>.
Thanks Cliff,
I got a windows machine and try to build C++ qpid client on it. But when I
try to build the example, it always failed at "stdint.h" file. I have tried
many different version of stdint.h file, likes boost/cstdint.hpp, or
pstdint.h. But neither of them can pass.
Could you tell me how to compile the examples on the windows machine?
On Sat, Feb 7, 2009 at 3:30 AM, Cliff Jansen (Interop Systems Inc) <
v-cljans@microsoft.com> wrote:
> In M4, the Windows C++ clients are built using static libraries. So each
> client program must duplicate the needed code from the client libraries.
>
> A small program like perftest (but which pulls in much client
> functionality) will be about 2.2Mb in size. Qpidbroker.exe is 1.6Mb.
>
> This will all change in M5 as dynamic library (DLL) support is being added
> to the Windows C++ port.
>
> Cliff
>
> -----Original Message-----
> From: chenta [mailto:chenta@gmail.com]
> Sent: Friday, February 06, 2009 9:12 AM
> To: users@qpid.apache.org
> Subject: Re: About footprint size
>
>
> Thank you Carl.
>
> I think I shouldn't use "footprint" right here. What I need to know is if I
> install a c++ client on a computer, how many disk space do I need?
> I already build the c++ client library on my linux machine. And I have the
> following assumption: When using dynamice link at run time. We need
> libqpidclient.so and libqpidcommon.so which is about 26 MB large. And I
> think sslconnector.so is needed when using SSL connection. Am I correct?
>
> What about the c++ client on windows system? I currently have no windows
> machine around. Could anyone help me to figure it out?
>
> Thanks,
> Chenta
>
>
>
> On Fri, Feb 6, 2009 at 9:32 PM, Carl Trieloff (via Nabble) <
> ml-user+168296-1934286974@n2.nabble.com<ml...@n2.nabble.com>
> <ml...@n2.nabble.com>
> >
> > wrote:
>
> > 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@...<
> http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2284115&i=0>
> >
> >
> >
> > ------------------------------
> > This email is a reply to your post @
> > http://n2.nabble.com/About-footprint-size-tp2279278p2284115.html
> > You can reply by email or by visting the link above.
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/About-footprint-size-tp2279278p2285298.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
RE: About footprint size
Posted by "Cliff Jansen (Interop Systems Inc)" <v-...@microsoft.com>.
In M4, the Windows C++ clients are built using static libraries. So each client program must duplicate the needed code from the client libraries.
A small program like perftest (but which pulls in much client functionality) will be about 2.2Mb in size. Qpidbroker.exe is 1.6Mb.
This will all change in M5 as dynamic library (DLL) support is being added to the Windows C++ port.
Cliff
-----Original Message-----
From: chenta [mailto:chenta@gmail.com]
Sent: Friday, February 06, 2009 9:12 AM
To: users@qpid.apache.org
Subject: Re: About footprint size
Thank you Carl.
I think I shouldn't use "footprint" right here. What I need to know is if I
install a c++ client on a computer, how many disk space do I need?
I already build the c++ client library on my linux machine. And I have the
following assumption: When using dynamice link at run time. We need
libqpidclient.so and libqpidcommon.so which is about 26 MB large. And I
think sslconnector.so is needed when using SSL connection. Am I correct?
What about the c++ client on windows system? I currently have no windows
machine around. Could anyone help me to figure it out?
Thanks,
Chenta
On Fri, Feb 6, 2009 at 9:32 PM, Carl Trieloff (via Nabble) <
ml-user+168296-1934286974@n2.nabble.com<ml...@n2.nabble.com>
> wrote:
> 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@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2284115&i=0>
>
>
>
> ------------------------------
> This email is a reply to your post @
> http://n2.nabble.com/About-footprint-size-tp2279278p2284115.html
> You can reply by email or by visting the link above.
>
>
--
View this message in context: http://n2.nabble.com/About-footprint-size-tp2279278p2285298.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: About footprint size
Posted by Carl Trieloff <cc...@redhat.com>.
chenta wrote:
> Thank you Carl.
>
> I think I shouldn't use "footprint" right here. What I need to know is if I
> install a c++ client on a computer, how many disk space do I need?
> I already build the c++ client library on my linux machine. And I have the
> following assumption: When using dynamice link at run time. We need
> libqpidclient.so and libqpidcommon.so which is about 26 MB large. And I
> think sslconnector.so is needed when using SSL connection. Am I correct?
yes, you can add and remove the .so's in the lib dir based on how you
want to strip it down
rdma, cluster, ssl, xml, etc can all be striped if you don't use the
feature to bring the disk size down
Min install in qpidd & common for broker & client & common for client
regards
Carl.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: About footprint size
Posted by chenta <ch...@gmail.com>.
Thank you Carl.
I think I shouldn't use "footprint" right here. What I need to know is if I
install a c++ client on a computer, how many disk space do I need?
I already build the c++ client library on my linux machine. And I have the
following assumption: When using dynamice link at run time. We need
libqpidclient.so and libqpidcommon.so which is about 26 MB large. And I
think sslconnector.so is needed when using SSL connection. Am I correct?
What about the c++ client on windows system? I currently have no windows
machine around. Could anyone help me to figure it out?
Thanks,
Chenta
On Fri, Feb 6, 2009 at 9:32 PM, Carl Trieloff (via Nabble) <
ml-user+168296-1934286974@n2.nabble.com<ml...@n2.nabble.com>
> wrote:
> 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@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2284115&i=0>
>
>
>
> ------------------------------
> This email is a reply to your post @
> http://n2.nabble.com/About-footprint-size-tp2279278p2284115.html
> You can reply by email or by visting the link above.
>
>
--
View this message in context: http://n2.nabble.com/About-footprint-size-tp2279278p2285298.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
Re: About footprint size
Posted by Carl Trieloff <cc...@redhat.com>.
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