/warm servers. I bet you could even solve
99% of the cases by simply waiting 3 minutes before serving a request.
Of course, I still love the GAE :)
Baz
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to
radually goes from 1 instance
to 11 - have I received the benefit of a warmed instance at every step of
the way? Is my twelfth instance now the "warm" one?
Cheers,
Baz
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" gro
at the threshold of instances and
oscillating back and forth between two instances. Whatever the situation, if
the solution were generalized like that, and most importantly not tied to a
SPECIFIC NUMBER of instances, it would be up to the user to decide how
important it was for them and whether to ena
>
> I do not understand why there is not at least a way to keep the apps
> running. I would even pay for that.
On deck is the ability to pay for and have reserved a warmed instance:
http://code.google.com/appengine/docs/roadmap.html (3rd bullet)
Baz
--
You received this message be
ass the 30
second limit, you will probably be able to use "Background servers capable
of running for longer than 30s" (
http://code.google.com/appengine/docs/roadmap.html)
Cheers,
Baz
On Tue, May 18, 2010 at 8:43 AM, Ravi wrote:
> Thanks Li for looking into it.
> For me 1-2 min
For a work-around you can cron a hit to your site every minute to keep it
live.
On Wed, Jul 7, 2010 at 11:01 AM, Jake wrote:
> Hey,
>
> Are you getting frequent instance restarts? Check the log for loading
> requests. This has been known to happen on sites with little-to-no
> traffic.
>
> Solu
Hello,
I have a non-user triggered process that queries the datastore for a dataset
of about 100k records, then loops through each record to update two other
entities in the datastore. What would be a good way to go about doing this?
I'm concerned about timing out and/or consuming more resources t
