Re: [google-appengine] Re: Bug in Cloud Console

I completely agree and the engineering team is working hard on providing better Stackdriver metrics to report container level resource usage (currently no ETA for the release). For clarity, currently it is the ' bytes_used ' me

Re: [google-appengine] Re: Bug in Cloud Console

On Sun, Mar 25, 2018 at 12:24 AM, 'Jordan (Cloud Platform Support)' via Google App Engine wrote: > > For an example of how to analyze the JVM heap usage you can review this > third-party > code snippet >

Re: [google-appengine] Re: Bug in Cloud Console

You are correct, that is indeed the memory usage of the entire instance. As previously mentioned, the best way to confirm what exactly is using all of that memory is to SSH into the instance and list the stats of each process. If it is Docker that is consuming the memory (which it most likely is

Re: [google-appengine] Re: Bug in Cloud Console

On Thu, Mar 22, 2018 at 7:49 AM, Attila-Mihaly Balazs wrote: > If I had to take a guess, I would say that this is because the JVM doesn't > really give back "free" ram to the OS (but it's still available for reuse > from within the JVM). So the console is showing the "OS" level metric while > que

[google-appengine] Re: Bug in Cloud Console

If I had to take a guess, I would say that this is because the JVM doesn't really give back "free" ram to the OS (but it's still available for reuse from within the JVM). So the console is showing the "OS" level metric while querying it directly shows the view from "inside" the JVM. Attila --

[google-appengine] Re: Bug in Cloud Console

Instead of checking the memory usage of your application's runtime (aka the Docker container that is running your application) you should log into your GAE instance (via ssh) and check the memory usage of the actua