Yeah, I refreshed pages over and over, and almost 1 out of 10 requests
where 'startup' priced. Which doesn't correlate to the response that
if you keep the instance up it will not open another instance. My
guess is multiple servers just get the request maybe with slight
preference to use an alre
Hello Jason,
I am also using spring and I experience the same issue. Initializing
Spring FrameworkServlet takes about 15 seconds. Going back to plain
old servlets sounds like a bad idea to me.
Isn't there any other way to speed this up? Maybe using memcache?
Cheers,
Tobias
On Oct 23, 5:53 pm
Hi David. What is your application's ID?
- Jason
On Wed, Oct 21, 2009 at 3:46 PM, david.zverina wrote:
>
> Keeping steady HTTP traffic does not work either. I have a script
> which 'http pings' my application every 30 seconds. Yet my app-engine
> instance experienced 70 spin downs yesterday alon
Keeping steady HTTP traffic does not work either. I have a script
which 'http pings' my application every 30 seconds. Yet my app-engine
instance experienced 70 spin downs yesterday alone!
I am REALLY looking to this update - until then I'd highly recommend
staying away from Spring!
On Oct 21, 6:
Aside from keeping steady HTTP traffic to your site, I'm afraid not. But as
I wrote in my last post, we're making updates over the next few releases to
drive this startup time lower.
- Jason
On Tue, Oct 20, 2009 at 2:06 AM, Marcel Overdijk
wrote:
>
> Is there any other way to keep an instance "w
Is there any other way to keep an instance "warm"?
Startup of instance just takes to much time to have an effective GAE/J
application...
On 19 okt, 22:58, "Jason (Google)" wrote:
> To answer your question, no, having a cron job run every minute to keep an
> instance warm will not work. If all a
Java startup cost is way too heavy and unusable on appengine. I'm
considering learning python now for the time being.
On Oct 19, 1:58 pm, "Jason (Google)" wrote:
> To answer your question, no, having a cron job run every minute to keep an
> instance warm will not work. If all application instanc
To answer your question, no, having a cron job run every minute to keep an
instance warm will not work. If all application instances have spun down,
then a fresh HTTP request will require a new instance to be created, which
will incur the startup costs.
- Jason
On Fri, Oct 16, 2009 at 6:45 AM, To
In general, and as the numbers that you've shared also back up, spinning up
a new instance of a Java application does take more resources, both CPU and
time, than starting up a new Python application. We are making back-end
improvements in the next couple of releases to improve these times,
partic
