Hi
Please find my answers inline.
Jeanfrancois Arcand wrote:
>>Salut,
>>
>>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?
I have tried this out using grizzly-comet-webserver-1.9.17-SNAPSHOT.jar but
I found the results exactly same.
I have added a Timer in the init method of the AjaxCometServlet to send 1
message per second to each client.
Modified Servlet :
http://www.nabble.com/file/p24310397/AjaxCometServlet.java
AjaxCometServlet.java
Test Case Program :
http://www.nabble.com/file/p24310397/StreamTest.java
StreamTest.java
100 Clients
http://www.nabble.com/file/p24310397/heap_dump_100_clients_comet.jpg
heap_dump_100_clients_comet.jpg
200 Clients
http://www.nabble.com/file/p24310397/heap_dump_200_clients_comet.jpg
heap_dump_200_clients_comet.jpg
>>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.
>>
What I'm saying is that in a Dead simple streaming application like this, if
there are 10,000 concurrent clients this byte[] will take more than 1.7 GB.
The byte[] consists of 80% heap. So the heap size of the app will be around
~2.2 GB, just for the grizzly part of it.
Now in case of a real world application like a streaming quote server which
is getting like 50,000 quotes per sec and streaming this data to around
10,000 clients, the memory consumption will be huge.
Thanks Again,
Abey Tom
>>Thanks!
>>
>>--Jeanfrancois
--
View this message in context: http://www.nabble.com/grizzly-http-servlet-deployer---High-memory-Consumption-%281---1.2GB-%2C--2000-3000-clients%29-tp24290149p24310397.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.
