Hi, My application get a lot of high-CPU usage warnings on the production server. I have spent the past few weeks profiling and optimizing my production code as suggested.
>From profiler data, I know that 99% of processor time is spent in Model.put or db.put. As a result I have been aggressively eliminating unnecessary or duplicate write operations. For instance in my most processor intensive http request, I have cut down the number of entities I update from 5 to a varying number between 0 and 3 depending on what absolutely must be updated. I also batch writes by using db.put() instead of separately calling Model.put(). As a result, I have cut the number of mcycles down from 7000+ to an average of around 2000 mcycles. However, I still get high cpu warnings on one http request, because it absolutely needs to update 3 separate entities (two node entities in a directed graph, and a sharded counter entity). So my question is, what else can I do to further optimize this specific section of code? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
