Timeouts can happen on even the simplest of datastore operations. As I understand it when a timeout does occur on a transaction (including a single put as there is a transaction there underneath) there is a lot of extra processing due to retry attempts.
On Oct 13, 11:40 pm, Roy Leban <[EMAIL PROTECTED]> wrote: > This might be bug 764 (http://code.google.com/p/googleappengine/issues/ > detail?id=764) but I'm not sure. > > Sometimes, I get timeouts that don't make sense. For example, > refreshing my home page (sometimes, when it happens to include a > single database write). > > 0-13 05:58PM 18.196 / 500 4180ms 10883mcycles 5kb > .... > File "myfile.py" ... > some_entity.put() > File "/base/python_lib/versions/1/google/appengine/ext/db/ > __init__.py", line 618, in put > return datastore.Put(self._entity) > File "/base/python_lib/versions/1/google/appengine/api/ > datastore.py", line 162, in Put > raise _ToDatastoreError(err) > File "/base/python_lib/versions/1/google/appengine/api/ > datastore.py", line 1627, in _ToDatastoreError > raise errors[err.application_error](err.error_detail) > Timeout > > It's looking like the 10883 megacycles is 20-50x a typical load of my > home page. Anybody have any ideas? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
