I have profiled the code. The problem with profiling is that the top CPU consuming calls appear to be part of the appengine framework, nothing I can do anything about. Also I don't understand how to correlate the information from profiling directly to mcycles. Just putting debug calls and looking at the timestamps tells me that most of time is taking place when I call put. I would like to record mcycles for each logging.debug call. Maybe I can add some calls using the profiler but I haven't figured out how to do that.
On Thu, Oct 16, 2008 at 11:29 AM, Mahmoud <[EMAIL PROTECTED]> wrote: > > You might want to profile your code: > http://code.google.com/appengine/kb/commontasks.html#profiling > > On Oct 16, 12:04 pm, "Ethan Post" <[EMAIL PROTECTED]> wrote: > > I would like to include the # of mcycles consumed in some of my logging. > At > > the moment it a put to two entities has occasional timeouts and the > number > > of mcycles appears to fluctuate for essentially the same put. I would > like > > to add some logging to see if this is the case and if so what the > variations > > are. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
