This is typically not Wicket initialization. The quickstart starts up in less than two seconds. You need to look at your domain / service / data layers. It's typically Spring / Hibernate loading / initializing that takes a long time (I've seen apps that take many *minutes* to start up).
-- Jeremy Thomerson http://www.wickettraining.com On Mon, Apr 19, 2010 at 4:19 PM, Esteban Ignacio Masoero < emaso...@getsense.com.ar> wrote: > Hi there: > > I know it's not THAT slow, and every presentation framework has it's > "loading time", but in my case this is affecting me in a much worse way and > there's no other solution for now. > Can any wicket expert tell me what can I do (anything: pre-compile > something, do something lazily, avoid something, etc) to speed up wicket > initialization? In GAE environment it takes up to 10 seconds from the > moment > I see the log entry "Started Wicket in deployment mode". > > I provide more details about my problem below. > > Thanks, > > Esteban > > My Problem: > I'm using GAE and currently there's a problem that when your app gets few > traffic, it gets "cycled out" (kicked out of the jvm) after a few minutes > of > not being accessed by anyone. So when your app (as mine) gets few visits, > almost every visit takes up to 10 seconds because wicket initializes every > time. There has been a number of solutions proposed: > - Run a cron job to visit the app so it's kept "warm". This is discouraged > from Google guys, as it would take all of us to the Tragedy of the Commons > ( > > http://groups.google.com/group/google-appengine/browse_thread/thread/22692895421825cb/ > ) > - Pay to reserve a JVM (not available yet, > http://code.google.com/p/googleappengine/issues/detail?id=2456 ) > - Do anything you can to optimize your initialization code (here I am!) >
