users@glassfish.java.net

Re: Excessive memory (280K) per connection in grizzly

From: Dominik Dorn <dominik.dorn_at_gmail.com>
Date: Tue, 19 Jan 2010 18:38:31 +0100

Does flushing the response help?

I think this is worth a bug report...

On Tue, Jan 19, 2010 at 5:35 PM, <glassfish_at_javadesktop.org> wrote:
> Hi,
>
> Anybody have an idea about this? Just for clarity, the http request results in a "long poll comet response" along with a bit of html. This is actually the comet example associated with the comet distribution in glassfish. We tried to manually run garbage collection via jconsole to see if memory would be released while the 10000 connections are waiting on a long poll response. No effect. 280K per connection is way too much, especially considering that we are transmitting data in the range of 1K/connection.
>
> Any suggestions? Should i write a bug report?
>
> Regards,
> John
> [Message sent by forum member 'lmcjome' (john.mezzetta_at_ericsson.com)]
>
> http://forums.java.net/jive/thread.jspa?messageID=381728
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>



-- 
Dominik Dorn
http://dominikdorn.com