The docs mention how to profile the code, which shows function calls and things.
How do you profile the datastore calls? (number of queries, read/ write, time, etc) Does anyone have some interesting ways to profile their apps? The application I have been designing seems fairly clean so far and I like the shape of our data, however I am worried about all the talk of timeouts and datastore issues. For example people saying that they can't create or delete 100 records in a 10 second request. That seems horrible. It seems like we have to treat the datastore in a very fragile way. Shouldn't the limited feature set of datastore allow us to pound on it much harder than a typical relational db like mysql? I haven't had issues on appspot with our app, but we havent been able to really test our app on it because our rich internet app needs more than 1mb files. Any code snippets or discussion about the fragile nature of datastore is welcome. -Mike --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
