You've received this message because you've subscribed to the Gaelyk Google Group.
To send an email to the group, please write to: gae...@googlegroups.com
To unsuscribe from this group: gaelyk+un...@googlegroups.com
To show more options: http://groups.google.fr/group/gaelyk?hl=en
One thing in particular that caught my attention and feels best about this blog engine is its blazing fast. I never experienced such responsiveness for groovy/gaelyk apps.
I checked source, seems to be caching magic in routes.
But how are you escaping the inevitable cold starts for such a new app (app id)? Is that because an url of this app is dzone'd and because of constant requests traffic the instance is always 'hot'?
If its just because of caching routes, that would just save loading and execution of groovlet/template servlet on startup.
That means, groovlet/template servlet are real cause of cold start time in gaelyk app? As I last observed, a barebone java app with servlet and jsp take about 1000 cpu ms while similar gaelyk app takes about 6000cpu ms to start.