Re: [Wrapper-user] what is the memory and cpu footprint of the wrapper itself?

[Leif M. <le...@ta...>]

Jennifer,
    Memory usage has been going up slightly with each release as new 
features are
added.   But I try to keep the footprint as small as possible.   One 
Windows,
3.1.0 requires around 1700KB this depends on the application and the 
output sent
to the console however.  Most internal buffers are dynamic.

    There was a slight performance hit in 3.1.0 when processing lots and 
lots of console
output.  This was caused by a fix to a synchronization problem with 
internal buffers
used by the logging system.   The hit was very minor however.
    What are you doing that you are even able to measure such a change. 
Even when sending lots and lots of output to the console the Wrapper CPU 
is still
usually down around 1-2% of total load.   When there is no output it 
always shows
as 0%

    As for the memory of your JVM.   The Wrapper requires a slight amount of
memory on top of what your application would normally use for its own 
classes,
but this is quite minor.   Your should be able to tune the max memory value
depending on your application.  I have small applications that run in 
just a few
MB where setting the max memory to 8MB works just fine.  Could probably
even be set to 4MB or so.

    Let me know if I did not answer you.

Cheers,
Leif

Jennifer Kolar wrote:

> For wrapper 3.1.0 and 3.0.5 under Windows 2000-- using sun's JVM 
> 1.4.2  what amount of memory do I need to allocate for the
> wrapper itself?
> Should I expect this number to be higher under 3.1.0?
>
> what about CPU usage. what % of CPU usage should I expect w/ default 
> configuration parameters?
> I am finding that the CPU load from 3.1.0 is about 20% higher from the 
> wrapper  than with 3.0.5.
>
> I am running multiple instances of processes wrapped with the wrapper 
> and thus can't just allocate a huge amount of memory to each process.
>
> Thanks,
> Jennifer