Before: / 200 9743ms 11464cpu_ms 264api_cpu_ms After: / 200 6894ms 7335cpu_ms 199api_cpu_ms
Better, but not really good enough. On Dec 11, 4:22 pm, Rusty Wright <rwright.li...@gmail.com> wrote: > http://googleappengine.blogspot.com/ > > See Dec 8 entry, "Request performance in Java". > > Brian wrote: > > I have 2 actions and something like 12 java classes total.. so don't > > think that is my problem. > > > Nicolas: What is this pre-compilation you speak of? Anything under 5 > > would be good enough for me... > > > On Dec 10, 9:41 pm, Timothy Spear <tsp...@green20now.com> wrote: > >> Brian, > >> I moved away from traditional Java MVC frameworks in GAE. The > >> overhead is way to high for all of them. > >> Instead I have moved to Flex for the front end with Java on the > >> backend. Very minimal server side structure with fast start times, > >> while the Flex application is downloaded the server is actually being > >> started via a javascript call to a bogus servlet. All of which make > >> the start/stop of the JVM on the GAE servers more transparent to the > >> user. > > >> Let me know if you need additional details. > > >> Good luck, > > >> Tim > > >> On Dec 10, 2009, at 3:46 PM, Brian wrote: > > >>> I have a app that I thought would be perfect for the google app > >>> engine. Mostly idle, but for periods could be fairly high demand. Very > >>> simple workflow, no user request should take more than 2 seconds > >>> server side. > >>> To prototype it out, I used the stripes framework to get a simple MVC > >>> setup. This works very well when it is up (<200ms server time per > >>> request), but is very very bad when the server needs to warm up to a > >>> new request (10-12 seconds). > >>> I know stripes is a very slow framework on server startup time, and > >>> apparently it needs to start up after being idle for a few minutes on > >>> GAE. Before I go down the patch of switching MVCs, I would be > >>> interested in > >>> a) What framework are you using > >>> b) What is the time taken from a cold start? (i.e. time to do a > >>> request when app is cold - time it normally takes to do the request). > >>> I am okay with a 3 or 5 second lag to get an instance going, but a > >>> 10-12 second hit is too much. > >>> If no framework gets much better, then I guess I will switch to a > >>> static index.html that loads the page via JavaScript. > >>> -- > >>> 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 > >>> google-appengine-java@googlegroups.com > >>> . > >>> To unsubscribe from this group, send email to > >>> google-appengine-java+unsubscr...@googlegroups.com > >>> . > >>> For more options, visit this group > >>> athttp://groups.google.com/group/google-appengine-java?hl=en > >>> . > > > -- > > > 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 google-appengine-j...@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine-java+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/google-appengine-java?hl=en. -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
