Starred it, thanks.
On Thu, Oct 16, 2008 at 4:30 PM, Josh Heitzman <[EMAIL PROTECTED]>wrote:
>
> Just opened http://code.google.com/p/googleappengine/issues/detail?id=789
> - API to get current mcycle consumption during request processing.
>
> On Oct 16, 9:04 am, "Ethan Post" <[EMAIL PROTECTED]>
Just opened http://code.google.com/p/googleappengine/issues/detail?id=789
- API to get current mcycle consumption during request processing.
On Oct 16, 9:04 am, "Ethan Post" <[EMAIL PROTECTED]> wrote:
> I would like to include the # of mcycles consumed in some of my logging. At
> the moment it a
I'm not aware of anyway to get the mcycle in code either. As a result
I've been breaking out little chunks of my processing and testing how
long each on takes and I've found that updating an existing entity
consumes no less then an average of 718 mcycles. And that's for an
entity with an empty S
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 a
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 timeo
