search

PiRSquared17 / app-engine-patch

Automatically exported from code.google.com/p/app-engine-patch
0 stars 0 forks source link

Integrate caching strategy in app-engine-patch #175

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Out of the box google app engine implements no caching, every request for
data hits the datastore with an attendant cost and chance of failure.

For applications with dramatically more reads than writes (as most
applications probably do), caching of results from the datastore is a good
strategy.

Attached is a class, that when plugged in dramatically reduces the cost of
data accesses.

The class was written by a Google employee (but is unsupported) 
http://groups.google.com/group/google-appengine-python/browse_thread/thread/a57a
1f85d3d60977

Original issue reported on code.google.com by jricket...@gmail.com on 28 Jun 2009 at 11:15

Attachments:

GoogleCodeExporter commented 9 years ago 
I made very bad experience with integrating other people's code because then I 
am 
responsible for maintaining it and I surely will get bug reports about this 
(e.g., only 
recently did someone add keys_only support, but I'm sure I would've had to do 
that if 
it were in app-engine-patch). Anyone can install this module at his own risk 
and IMHO 
that's absolutely sufficient.

Original comment by wkornew...@gmail.com on 28 Jun 2009 at 12:44