On Wed, Apr 22, 2009 at 12:53 AM, Alexander Kellett <lypa...@gmail.com>wrote:

> are you sure this isn't the gc poll?

It's not the GC ping

> i agree 10 seconds is too short
> (thats a lot of traffic...)

10 seconds, as Marius pointed out, is the periodicity of the app because the
clock is updating every 10 seconds.  This means that there's an update to a
comet component (the clock) every 10 seconds.

> , but its a very quick operation, its not
> an actual poll on the page afaiu

There's a very fast path in the code for the poll and it's all done over an
http keep-alive anyway.

If there's anyone who has an idea better than long polling for server to
client push (other than HTML 5/WebSockets), I'm all ears.

If the amount of traffic that long polling creates on your site because of
long polling exceeds your capacity (in my calculations, 100,000 active
sessions per dual core server machine), then you can remove the comet



> On Wed, Apr 22, 2009 at 8:54 AM, przemek.pokrywka
> <przemyslaw.pokry...@gmail.com> wrote:
> >
> > It is 10 sec actually at Comet chat example.
> > Not very good for high-traffic public portals.
> >
> > Przemek
> >
> > On Apr 21, 7:21 pm, "marius d." <marius.dan...@gmail.com> wrote:
> >> But what is the problem with long pooling if a request is done every x
> >> minutes (if server does not have any message for this client)?
> >
> > >
> >
> >

Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to