Hi all, I've spent a lot of time lately profiling my app. Basically, I've been looking for spots where optimizations can be done so that I better understand its state and figure out how soon I might need to look at 'Billing'
The thing I've noticed is that even if pluging in cProfile is a very easy job, figuring out what's going on is basically much more complex than I've imagined, due to the fact that there is no easy way to figure out the code execution path and due to the differences in the SDK sourcecode vs runtime. Anyways, there is one thing that I've learned: datastorage hits, even for reads, are not as cheap as advertised. So, now I'm trying to figure out what are the scenarios when a datastorage hit is required for reads. Here is my initial list: 1. Model.get(): 1 hit (even if multiple keys are provided) 2. db.get(): 1 hit (even if multiple keys are provided) 3. model.reference_property: 1 hit 4. Query.count(): 1 hit Are there any other scenarios that I need to account for? a. What happens for a Query.fetch()? I assume that is 1 hit too. I am wondering if iterating over the results will result in more roundtrips? b. Any other scenarios.... Many thanks in advance, ./alex -- .w( the_mindstorm )p. Alexandru Popescu --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
