[google-appengine] Re: datastore timeout every time - on reads, not writes

2009-05-01 Thread Wooble
On May 1, 12:28 pm, Liang Zhao wrote: > I'm not sure, but it seems both > > alerts = Alert.all().filter('expires >= ', datetime.datetime.now()) > > and > > alerts = Alert.all().filter('expires >= ', > datetime.datetime.now()).fetch(1000) > > should be the same, since according to documents, ap

[google-appengine] Re: datastore timeout every time - on reads, not writes

2009-05-01 Thread Liang Zhao
I'm not sure, but it seems both alerts = Alert.all().filter('expires >= ', datetime.datetime.now()) and alerts = Alert.all().filter('expires >= ', datetime.datetime.now()).fetch(1000) should be the same, since according to documents, app engine only return the first 1000 records. On Fri, May

[google-appengine] Re: datastore timeout every time - on reads, not writes

2009-04-30 Thread tayknight
I figured out that I needed to do a alerts = Alert.all().filter('expires >= ', datetime.datetime.now ()).fetch(1000) Apparently it is faster to do a fetch() than iterate over the values. On Apr 30, 7:28 pm, tayknight wrote: > Data is returned in development almost instantly. In production, the

[google-appengine] Re: datastore timeout every time - on reads, not writes

2009-04-30 Thread tayknight
Data is returned in development almost instantly. In production, the error is returned after about 4 seconds. I get the datastore error long before 30 seconds. On Apr 29, 9:08 am, Liang Zhao wrote: > Each request can only run 30 seconds in server side, > > but in development server, there is no

[google-appengine] Re: datastore timeout every time - on reads, not writes

2009-04-30 Thread Liang Zhao
Each request can only run 30 seconds in server side, but in development server, there is no limitation on it... On Wed, Apr 29, 2009 at 11:56 PM, tayknight wrote: > > And, I should add, this works perfecty (and quickly) from the > development server's datastore. > > On Apr 29, 8:31 am, tayknigh

[google-appengine] Re: datastore timeout every time - on reads, not writes

2009-04-29 Thread tayknight
And, I should add, this works perfecty (and quickly) from the development server's datastore. On Apr 29, 8:31 am, tayknight wrote: > I have a problem. I'm getting datastore timeouts when doing reads. The > code finished about 5% of the time. The code looks like: > > alerts = Alert.all().filter('