From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Tue, 07 Jul 2009 10:32:43 -0400

Salut,

apology for the delay. Can you file an issue and describe how to
reproduce the memory grow? We run really large test as part of GlassFish
v3 integration and so far we haven't measured such peak. So I want to
investigate how I can reproduce the issue locally and see what can be
improved.

Thanks

-- Jeanfrancois

Abey Tom wrote:
> I was testing a prototype application which is build on grizzly comet. I did
> a round of perf test on that and I would like to share the results. Please
> find the jconsole screen shots attached.
>
> Test Scenario:
> Total number of streaming clients - 3500
> Total Messages pushed from server per second : ~12500 to 13000.
>
> http://www.nabble.com/file/p24323801/grizzly_3500_clients_overview.jpg
>
> Here the CPU load is very less. I kind of feel that the heap memory is a
> little more than i expected.
>
> 1. Heap Space :
> http://www.nabble.com/file/p24323801/grizzly_3500_clients_heap.jpg
> grizzly_3500_clients_heap.jpg
> 2. Eden Space :
> http://www.nabble.com/file/p24323801/grizzly_3500_clients_eden_space.jpg
> grizzly_3500_clients_eden_space.jpg
> 3. Survivor Space :
> http://www.nabble.com/file/p24323801/grizzly_3500_clients_survivor_space.jpg
> grizzly_3500_clients_survivor_space.jpg
> 4. Old Gen :
> http://www.nabble.com/file/p24323801/grizzly_3500_clients_old_gen.jpg
> grizzly_3500_clients_old_gen.jpg
>
>
> Thanks
> Abey Tom
>