I use Play framework with GAE module, it works quite nice and performance is
ok.
Personally I don't have good experience with Spring roo
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
vraptor is fast, easy and RESTful ready
better startup time with guice or pico instead of spring
be sure to disable annotation scanning and setup your annotated components
manually
http://vraptor.caelum.com.br/en
On Sun, Jul 10, 2011 at 3:38 AM, Max thebb...@gmail.com wrote:
I use Play
for warm up issue, there are several options, including always on instance,
cron job, etc
you may want to take a look at this page http://www.keepyourappwarm.com/
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this
If you're just looking for an MVC framework, here are two that I wrote:
Tagonist: http://www.tagonist.org/
This is about as simple as it can possibly get. Less than 500 lines
of code, no classpath scanning, zero (as in nada, none, zip) effect on
startup time. It just plays clever with JSP.
Yep, that was my reaction, definitely not really good enough.
I'm using Spring and I've heard that it makes apps slow to start with all of
its instantiating and wiring things together. I've been meaning to search or
post a query on the Spring forums about things I could do to
On Sat, Dec 12, 2009 at 20:06, Rusty Wright rwright.li...@gmail.com wrote:
I'm using Spring and I've heard that it makes apps slow to start with all
of its instantiating and wiring things together.
Have you tried to lazy load your beans? In my local tests I have a very
fast startup.
I assume they aren't doing a full JVM startup every warm up, are they?
Seems they could load it into the JVM memory.. then page it out to
disk or something. Somehow has to be a way to keep it scalable to many
1000s of users, while not taking 7 seconds to wake up
On Dec 12, 8:20 pm, Rusty Wright
My guess is that they have some sort of soft undeploy which tells jetty to
purge the app's code and data from its memory (after some period of
inactivity). Then when a request arrives jetty re-loads the app (meaning a
full restart of the app). Each jetty might be supporting multiple apps.
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
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 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
I am using Stripes and I think the startup is not really that slow, I
usually
11 matches
Mail list logo
