I'm trying to figure out how to configure our GWT app to avoid latency. At
the moment, it isn't used much so the app loads new instances regularly.
We've got warmup requests enabled and have turned Always On on for all three
instances. At the moment, we don't have any servlets specified as
load-on-startup because it's a GWT app so we don't really need any
specifically loaded at start-up.
With this setup, we still see the following log message several times a day:
1.
1.
This request caused a new process to be started for your application, and
thus caused your application code to be loaded for the first time. This request
may thus take longer and use more CPU than a typical request for your
application.
Furthermore, on one particular page, we make two RPC requests to the server
in succession. This log message often appears for both calls which suggests
to me that they are each going to different instances and each one is
launching a new process for the app.
Is there something else we need to do to ensure the app remains loaded? We
see some serious latency (up to 8 seconds) when these log messages appear. I
was thinking we could have a dummy servlet that simply retrieves something
from the datastore to ensure the application code is loaded but that seems
like it shouldn't be necessary.
--
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 at
http://groups.google.com/group/google-appengine-java?hl=en.
