We definitely see lots of cases where a db.put() that normally takes <150ms suddenly takes >30s and times out. And it usually happens in bursts (i.e., many concurrent requests suffer the same fate). Seems to be only on taskqueue requests, but difficult to know for sure because taskqueue requests are perhaps 90% of our requests.
In fact, this is the source of _most_ of our errors. j On Nov 24, 1:03 am, Tim Hoffman <[email protected]> wrote: > Hi > > A single put ajax or otherwise shouldn't take to long, are you doing > the put inside transactions, with large entity groups? That could > cause problems. This isn't a big counter or something is it ? How long > is a single put taking ? and are you getting > a Datastore timeout or some other error ? > > Size/number of entities in datastore really doesn't make to much > difference, > > large entities with lots of indexes will affect your write time. > > Just confirming you are doing a somequery.fetch(n) on your query > results? > > Rgds > > T > On Nov 24, 12:43 pm, "Alexander W." <[email protected]> > wrote: > > > > > Yes I've looked at appstats, looks alright so far. > > > Problem 1: put() operations (ajax request) > > > It's one put() operation per request. > > > Problem 2: queries (normal requests) > > > It's important that the results of these queries are up to date, so I > > have to fetch them every time a user loads the application. > > > It's a simple query, but the db has more than 10M entries. -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
