Actually, even just fetching one entity by key will frequently cause a
Timeout. My logs are full of these...
On Apr 30, 2:59 pm, Sylvain sylvain.viv...@gmail.com wrote:
For my app, I never fetch more than 250 entities because I've seen
that if this values is bigger you raise too many datastore
Well, I've read a lot of posts about google datastore and the problems
with batch operations, relational approach to arrange data in bigtable
etc. but I always thought the problem wasn't in datastore itself but
in the way people use it. Now I can see with my experience that it
acts just in an
For my app, I never fetch more than 250 entities because I've seen
that if this values is bigger you raise too many datastore timeouts.
But even with 250 entities (with a very basic Kind) something I get a
timeout.
One funny thing is that you can fetch up to 1000 entities (whatever
kind, number
Today, my app has seen 2 timeout errors at 3:10 pm according to the
log. Each one was 30 seconds apart. One was a Get and the other a
Put. Each on totally different classes that are not connected in any
way.
On Apr 17, 4:15 pm, Brandon Thomson gra...@gmail.com wrote:
Google will not really
Hi,
I would just like to add myself into this, my app twitterautofollow (twollo)
regularly gets DataStore time outs on puts (in the most part). All my
entities are root entities.
I did have a thread open on this only a few days ago.
Paul
2009/4/17 Ray Malone rayish...@gmail.com
I'm seeing
Datastore timeout is one of the biggest (and oldest) issue with GAE
and mostly because it is random.
You can get it on get, put, fetch,... even with few entities.
I hope that soon, datastore timeout will be negligible. Currently, it
is not the case.
Regards
On 17 avr, 09:50, Paul Kinlan
Speaking only for my app, I can tell this is not an application
issue. My datastore is made up of only root entities and in most
cases works well quickly. My app doesn't see large volumes of
requests per second and it's more like requests per minute. There
is no possible way the errors I'm
Good for you that your company has good prospects. As somebody who has
built high traffic sites (co-founder of IGN.com), I offer some advice:
Don't even think about driving traffic to it unless it has been stable
for weeks. If you are having problems w/ minute traffic, you can't
imagine how bad
Google will not really acknowledge this as a problem or defect but
neither do they provide a lot of options for workaround. My experience
is that Timeouts do occur on about 0.5% of puts regardless of size of
entity. These are root entities. It is not caused by write contention
from multiple
On Thu, Apr 16, 2009 at 4:16 AM, DarkCoiote darkcoi...@gmail.com wrote:
On Apr 15, 3:26 pm, Jeff S (Google) j...@google.com wrote:
Hi Ray,
Which operation was is that timed out (get, query, put)? Also, how
consistently are you seeing these timeouts?
I generally recommend catching
Yes... I've read that...
The problem with using all entities as root is that I'm unable to use
transactions as it is... I would have to code a lit bit... although
I just found a paper describing a project that seems really good.
http://danielwilkerson.com/dist-trans-gae.html
I think it will be
I'm seeing random timeouts where there are many seconds or minutes
between requests and hours before app engine handled the same request
within 400ms. I hit another one today that will actually cost my
business, not much but some. My app needs to catch these and I am on
many pain points.
Hi Ray,
Which operation was is that timed out (get, query, put)? Also, how
consistently are you seeing these timeouts?
I generally recommend catching datastore timeouts and handling them in a way
that makes sense for your app. There are currently occasional (quite rare as
a percentage) timeouts
13 matches
Mail list logo
