You might want to star the following issues :
Issue 7865 http://code.google.com/p/googleappengine/issues/detail?id=7865 :
User-facing
requests should never be locked to cold instance starts
Issue 5755 http://code.google.com/p/googleappengine/issues/detail?id=5755 :
Custom
Scheduler API
Issue
Right about the time i noticed the scheduler had started cycling instances
every 3-4 minutes, I also noticed that our QPS has dropped to 30% of what
it used to be.
Instead of ~1 QPS average we now have 0.3 QPS average.
Seems to be the same for Master/Slave and HR datastore apps.
Anybody else
I am also seeing this issue on OSX
On Thursday, 29 November 2012 15:09:43 UTC+10, vivpuri wrote:
Our team is also facing this issue. Mac OS 10.8.2 with SDK 1.7.3 and also
on Windows 7.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To
From the NDB async docs:
Furthermore, instead of using acct = key.get() or
acct = key.get_async().get_result(), the function should useacct = *yield*
key.get*_async*(). This yield tells NDB that this is a good place to
suspend this tasklet and let other tasklets run.
Re the second example:
hi all,
We're having a G+ hangout on Wed. Dec. 5th, 4pm-5pm (US / Pacific), to chat
with several members of the App Engine Team about the new experimental
development server for Python (see this thread from a few days ago:
http://goo.gl/t711k). Submit your questions here: http://goo.gl/XDH7E,
