The queries (or any other operation for that matter...) have grate
latencies (or 500 error code) for about 20 percent of the time.
For example the same query that yesterday or 2 days ago took about 2
seconds, now takes between 5 and 25 seconds (the SAME query). The app
can work fine, with low late
First of all, i realized that part of the problem was the range of the
query (my data objects/entities grew very fast so i didn't that i was
retrieving 1000 entities per query). But my pb is that i don't really
"get it" ... the difference in time between queries is very different
from moment to mom
It seams now that the tests run in the last 2-3 days are more
homogeneous. I believe that the high latencies that affected my tests
(and caused so different results for the same cases) are the ones that
affected the other applications as well. I don't get the 500 error
code now and the behavior se
What does the query look like? Query performance can sometimes be affected
by the "shape" of the data - that is, if the data changes, it may change the
number of indexes we need to zig-zag over.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
There are definitely high traffic times and low traffic times, but I would
be surprised if it had a significant impact on the performance of your
application. Can you track this with metrics and keep us posted? When you
say "10 or 25", what are you referring to? Entities? Milliseconds?
--
Ikai Lan
seconds :)
On Fri, Oct 22, 2010 at 8:48 PM, Ikai Lan (Google)
> wrote:
> There are definitely high traffic times and low traffic times, but I would
> be surprised if it had a significant impact on the performance of your
> application. Can you track this with metrics and keep us posted? When you
