A pure GWT application is a lot less demanding on server side resources as most of the UI processing is off loaded to the client. Also, a problem that I have run into with running a traditional web framework on GAE is that "loading requests" can take a long time and cause requests to be aborted (if longer than 10s). That is, the first hit must load your app onto a server instance and Wicket, in my case, is taking some time to initialise. GWT only requires a lightweight servlet to respond to RPC calls which is much faster to load.
On Dec 19, 7:05 am, James H <[email protected]> wrote: > I began using GAE for a project earlier this year and am aware of the > throughput documented in the GAE docs and this forum. Now, I am > considering using GWT as the front-end to my GAE application. > > Can anyone share their experience in regard to performance when using > GWT with GAE? For example, does GWT introduce alot of overhead as > compared to a Struts/JSP solution? > > Can anyone share their experience in regard to CPU Quota usage when > using GWT with GAE? Or any other resource quota related? > > Given a 1000 or 10,000 simultaneous users, what would their response > time be like when comparing GWT vs Struts/JSP both on GAE? I need GWT > on GAE to support the potential for a very large number of > simultaneous users. > > Thanks, J -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-appengine-java?hl=en.
