On Tue, Jan 27, 2009 at 01:42, [email protected] < [email protected]> wrote:
> > I never said it cretaed multiple instances, simply a new thread per > request. > *sigh*. I must not have had enough coffee in the morning before replying to your post. I read "thread" as "instance" in your original post. Sorry. > On Jan 23, 4:30 pm, Shawn Pearce <[email protected]> wrote: > > On Fri, Jan 23, 2009 at 08:17, [email protected] < > > > > [email protected]> wrote: > > > > > Standard servlets create a new thread per request but from a few > > > simple test i have run this appears not to be the case with GWT. > Like what everyone else has already said; each concurrent request runs on its own thread, but that thread isn't necessarily new. Most containers recycle threads as thread spin-up/shutdown are relatively expensive operations. Pooling threads and recycling them across requests reduces the per-request overheads imposed by the container, allowing applications to use a larger percentage of the CPU, and the per-request latency target the developer is shooting for. E.g. in my latest GWT based application, I was trying to hit <200 ms latency. The more of that time that is available to the application, the more useful work I can do within that window. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
