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 sp
On 1 June 2011 14:54, Bart Thate wrote:
>
> 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 monito
Oi Robert ;]
responses below
@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.com
On Wed, Jun 1, 2011 at 6:45 AM, Robert Kluin wrote:
> There have been one or two other threads where this has been suggested
> as well. I originally had a similar thought,
There have been one or two other threads where this has been suggested
as well. I originally had a similar thought, but after some thought I
honestly think it sounds very complicated, you'll have both CPU hours
and memory-meg-hours (or whatever).
I sometimes see much higher memory usage than expe
I'd prefer this over the instance billing as well
On May 31, 8:36 pm, Bart Thate wrote:
> Greetings !
>
> As i understand it this whole move of Google is because they discovered that
> it is the memory occupied thats is the cost factor requiring this drastic
> move. So if that is the case why not
