Configuring JVM options during deployment currently isn't possible with the Cloud SDK, but it does sound like a good feature request to make on the issue tracker <https://code.google.com/p/google-cloud-sdk/issues>.
It is possible to rebuild the runtime docker image from source however (see the github project links <https://cloud.google.com/appengine/docs/flexible/custom-runtimes/build#configuring_the_dockerfile>) and insert your own JVM options into jetty_cmd.sh so this may be one way to enable native memory tracking or JMX on the deployed instance. I've only done minimal testing on this myself though. On Saturday, June 25, 2016 at 3:14:20 PM UTC-4, Joshua Fox wrote: > > I suspect a "leak" in my Java application on App Engine Flexible > Environment and I'd like to trace memory, as I would do with JProfiler, > YourKit, or VisualVM on my local machine. Heroku has some functionality > for this. <https://devcenter.heroku.com/articles/java-memory-issues> > > I'd like to trace the classes, allocation point, and path to GC root for > objects allocated during a certain action, for which I set checkpoints. Or > if that is not possible, I'd like a heap dump of the (enormous) memory of > my instance. > > How can this be done in App Engine Flex Environment? > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/705209d9-94c0-4660-9108-7ed32a2c1f42%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
