Salut,
Abey Tom wrote:
> Hi,
>
> I'm doing a perf test using
> grizzly-http-servlet-deployer-1.9.17-SNAPSHOT.jar with the sample
> application grizzly-comet-chat.
> I start the server by
>
> java -jar grizzly-http-servlet-deployer-1.9.17-SNAPSHOT.jar -p 8181 -a
> target/grizzly-comet-chat.war --cometEnabled=true
Can you rerun your test using:
java -jar grizzly-comet-webserver-1.9.17-SNAPSHOT.jar -p 8181 -a
target/grizzly-comet-chat.war com.sun.grizzly.samples.comet.AjaxCometServlet
I just want to make sure the issue is not caused by the deployer (I
doubt). Can you also share your load test?
Noe that if the link you stress is the connection that gets suspended,
this is normal to see the heap going up a little as those connections
state are stored/persisted.
Thanks!
--Jeanfrancois
>
> The server is taking around 1 GB of heap space on 2000-3000 concurrent
> clients which I feel is a little high.Or is it expected to work like this?
> I used Java VisualVM and took a heap dump. I have attached the screen shots
> of the same.
> In the heap dump I can see a byte[] which itself takes around ~17MB per 100
> connections and remains constant.Can we optimize this some how?
>
> Below is the attached screen shot of the heap dumps.
> 1. Startup 0 clients:
> http://www.nabble.com/file/p24290149/heap_dump_idle.jpg heap_dump_idle.jpg
> 2. 100 clients :
> http://www.nabble.com/file/p24290149/heap_dump_100_clients.jpg
> heap_dump_100_clients.jpg
> 3. 200 clients :
> http://www.nabble.com/file/p24290149/heap_dump_200_clients.jpg
> heap_dump_200_clients.jpg
> 4. 300 clients :
> http://www.nabble.com/file/p24290149/heap_dump_300_clients.jpg
> heap_dump_300_clients.jpg
>
> I have attached the screen shots bcos the dump file is large (even zip).
>
> Can we optimize this some how? Kindly let me know.
> Thanks
> Abey Tom
>
>
