Hello there, I delegate the construction of my singleton PersistenceManagerFactory (PMF) (for data exchange with the datastore) to a queued task, since this operation can take a few seconds. This way, my home page can show without waiting for PMF construction to be complete.
I know that the first request to a GAE server will require the starting of a new JVM (and Wicket application instance) and can take many seconds to be served. If a Wicket application instance receives no request for "a while" then the JVM can be shut down. I think that stuff may be serialised to persistent storage since data in my Wicket sessions survives such JVM shut-downs. Anyway, I know that some people create cron jobs or queued tasks to poke the web application regularly, in order to stop the JVM shutting down and to maintain the fast serving of web pages. Is this any help? intmanch wrote: > > I've been actively using wicket on GAE for quite a lot of months and I > love it, but I've quite serious performance problems. I already checked > all > the advices to speed up the performance but still is quite slow specially > for some requests or opening a bookmarkable page. > -- View this message in context: http://old.nabble.com/Wicket-GAE-performance-tp28118591p28119597.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
