It's not recommend to write more than 20 entities in one request, and I don't think you will exceed it in a common request.The datastore has such a limitation of writing, you can't treat it as a relationship db. (In my test, it takes about 1 second to put 100 simple entities into db.)
However, sometimes we may meet this situation. My suggest is to limit the number of entities as possible, use "db.run_in_transaction" to keep entities correct and complete saved to db. If possible, AJAX calls can help you breaks a big transaction into several small transaction. And you can set how many times the transaction should try when operation fails, so you can give a failed message to user before timeout. 2009/4/15 Sylvain <[email protected]> > > Hi, > > Currently, I think 0.5% of my Datastore operations result in a > datastore timeout. > I don't know why... It can be raised on very simple or very > complicated operation. > > For my app for example, the problem is that it can occur during a big > request where I need to create 50-100 entities of 3 different kinds. > So I need to manually rollback everything and it can be difficult. > > Having a "big" transaction could be a solution, but GAE it too limited > (only 1 kind,....). > > It seems that datastore timeout will always be there and we have to > manage them. So I think we need an article that explains how to handle > them properly with different scenarios. It will be very appreciated. > > Regards. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
