I've already posted this on the Java GAE group, but maybe someone has
seen this issue on a Python-hosted app.
I'm carrying out some testing of my app against the HR-store, instead
of the M/S datastore, and I've noticed that occasionally I'll get a
request which has a massive CPU spike. These
I'm tuning for the hr.
update entities are fast
entities with 3 properties add, delete 149ms 101cpu_ms 84api_cpu_ms
(tested over more days)
entities with 25 properties
http://code.google.com/p/relat/source/browse/trunk/relat/e-comm/contactmodel.py
add, delete 1825cpu_ms 1807api_cpu_ms (tested over
Just to emphasise, I'm seeing these spikes on requests which don't hit the
datastore at all, and I don't see the same spikes on the same app with the
datastore set to M/S.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this
Hi Simon,
I'm glad your mention the subject, to get a spead gain i moved out all
the transaction surrounding where possible before testing the hr
datastore.
But it seems optimized for transactions because it is much faster in a
transaction. After putting all put actions in a transaction the kind
