Hello, Currently I made a memcache layer over my DAO to prevent calling the datastore if it is not neccessary. Do I understand right, that this L2 cache is doing exactly the same? If I e.g. fire a request and then fire the same query again (and in the mean time no update or delete was done) it would take it from the cache instead of doing the datastore call? Or is this someting else? Why is it not disabled by default (are there draw backs)?
Thanks, Toby On Mar 6, 12:39 pm, datanucleus <[email protected]> wrote: > > Is it possible that DN L2 caching in GAE drives down CPU milliseconds > > used but overall response times get slower? > > Benefits of an L2 cache are subject to what you're doing (it's benefit > is for multiple PM's for a PMF accessing the same objects, and hence > providing a "quick" way of accessing them). Obviously the log tells > you timings of everything related to it. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
