Hi Robert,
I got it!
I have not considered that query offset also causes small operation.
thank you very much Robert for your input.
On Wed, Feb 1, 2012 at 9:00 AM, Robert Kluin robert.kl...@gmail.com wrote:
Hey Andrew,
So you need to remember that running a query will result in many
Hi Robert,
Thanks for you being interested to help me.
Let me tell my long sad story:
I have Java appengine app.
The app has only one page. This page performs search with various
parameters, fetches 11 entities and displays search result.
My app has 3400 page views per day and each day it
Hey Andrew,
So you need to remember that running a query will result in many reads
(the number of results, plus a scan iirc) -- not just one. That could well
be the source of your problem.
As for why memcache isn't being effective, that's harder to say; that
could be a coding issue or a
Hi Robert,
no,
session disabling is the first thing I did to reduce datastore access count.
See
http://code.google.com/p/rent-map/source/browse/trunk/trunk/src/main/webapp/WEB-INF/appengine-web.xml
Second thing I did was memcache introducing. So I used all standard
datastore friendly technics.
Hey Andrew,
What symptoms are you seeing exactly?
Robert
On Mon, Jan 30, 2012 at 05:48, Andrew Osipenko dev7...@gmail.com wrote:
Hi Robert,
no,
session disabling is the first thing I did to reduce datastore access count.
See
Hi Frank,
Have you solved it?
I have nearly the same problem.
I think that appstats do not count some datastore read operations. I
thought my application accessed datastore during intialization before
appstat filter is being invoked. But I can't find anything bad during my
app
Are you using sessions?
On Sun, Jan 29, 2012 at 05:37, Andrew Osipenko dev7...@gmail.com wrote:
Hi Frank,
Have you solved it?
I have nearly the same problem.
I think that appstats do not count some datastore read operations. I thought
my application accessed datastore during
