Hey Greg,
As I recall that API just returns the current total and average
memory used by the instance, right? That is helpful for debugging
memory usage, but trying to guess what part of the machinery caused
the memory usage to spike between calls is still guessing. Just
trying to guess if a spike was caused by something in the SDK or our
own code could pose a significant challenge. Or am I missing
something?
I'm thinking some tool like Tobias' Apptrace would be quite helpful:
http://code.google.com/p/apptrace/
Robert
On Wed, Jun 1, 2011 at 01:36, Greg Darke (Google)
<[email protected]> wrote:
>
>
> On 1 June 2011 14:54, Bart Thate <[email protected]> wrote:
>>
>> <snip>
>> Once memory is billable, you gonna be sure that people actually try to
>> make good use of it. If you do instance price only who cares ?
>> As for debugging you might have point maybe google could provide the an
>> app stats API where the app could monitor its memory usage itself (or is
>> there already such a API) ?
>
> You can use the google.appengine.api.runtime api to determine how much
> memory you are currently using
> (http://code.google.com/appengine/docs/python/backends/runtimeapi.html).
>
> --
> 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.
>
--
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.
