memcache
http://code.google.com/appengine/docs/python/memcache/usingmemcache.html
On Nov 26, 11:54 am, Martin Dvorak martin.dvo...@mindforger.com
wrote:
Hi all!
I'm looking for a lesson from 'pricing oriented programming'. My service
has a REST-style endpoint that I use to
Hi,
Your problem actually may be the counts - read this post by Alfred, who is
part of the datastore team I believe.
https://groups.google.com/d/msg/google-appengine/LsVSKbFCLwI/FpYEd1fPFLYJ
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google
Obviously I use memcache through the application. Unfortunately this is not
solution to my problem as the export I described above is typically used
for backup before upgrades and majority of entities is read occasionally.
It may be that I'm wrong. Is it a best practice to have a custom write
Obviously I use memcache through the application. Unfortunately this is not
solution to my problem as the export I described above is typically used
for backup before upgrades and majority of entities is read occasionally.
It may be that I'm wrong. Is it a best practice to have a custom write
Thanks, I have read this post before I sent my question to the group.
However it 1 count() operation is much more cheaper that loading one
entity (that in the collection I checked takes ~7 Datastore Key Fetch Ops on
average).
Actually I need to reformulate the question I originally asked:
