Thanks Nick.
I was so pee-ed off thinking about this earlier, wondering why I
couldn't find more about it, and I held a tiny hope that maybe it was
because it had been removed as an issue, more or less. So this is
something of a relief!
I guess the next question is along the same lines of Ulrich'
I am curious about how this works too. I've bumped up against this
limit in the past when the datastore is acting up and rpcs start
taking multiple seconds to return.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, se
I'm also interested in how this works.
On Apr 11, 2:15 am, Brandon Thomson wrote:
> I am curious about how this works too. I've bumped up against this
> limit in the past when the datastore is acting up and rpcs start
> taking multiple seconds to return.
--
You received this message because yo
Hi Nick,
This is a little disconcerting - would it be fair to say that if I
were using the pattern you documented here
http://code.google.com/appengine/articles/deferred.html,
then my latencies would not be low (since I am pushing the
DeadlineExceededError on every deferred operation), and my
this is exactly what I'm seeing with the Task Queue as of yesterday.
it was ripping fast 2 days ago, I was getting close to 150 features/
second upload/index. now this has dropped considerably and there are
many timeouts on the TQ after only 10secs (startup time, not even
hitting my code).
http://
There is a lot of stuff on the roadmap which might represent a
different approach to the problem
http://code.google.com/appengine/docs/roadmap.html
especially -
- Background servers capable of running for longer than 30s
- Support for mapping operations across datasets
and maybe these -
- Abil
