Did you manage to test this any more Paul?
I've just been stung with this again - 3 instances left inert for a
couple of days. Three requests which should have consumed 8 seconds
of CPU time consumed almost 200 seconds!
On Feb 11, 11:41 pm, Paul Verhelst
paul.verhe...@cabinetsensesoftware.com
That's really interesting Paul - I've noticed a very similar problem on
instances which aren't Always On but haven't been recycled (reported at
this
Linkhttps://groups.google.com/d/msg/google-appengine/VEifURis4OI/-kmdlQh7AXgJ
)
I've noticed the following CPU costs to my app when it's left
That makes sense. I'm going to leave my process for 24 hours and then fire
a transaction. I'll report on my findings.
Is there a way that we can fire a startup request in the background that
initiates the process unbeknownst to the user? If it can take the several
second hit it needs to
On 11 February 2011 17:33, Paul Verhelst
paul.verhe...@cabinetsensesoftware.com wrote:
That makes sense. I'm going to leave my process for 24 hours and then fire
a transaction. I'll report on my findings.
Is there a way that we can fire a startup request in the background that
initiates the
Thanks Barry, that's exactly what I was looking for. There's a bit of a
catch-22 situation here though. My app is serving very little traffic at
the time and according to the docs, appengine will always serve a load
request in that case... and the only solution is to use always on... but
