Unfortunately, the RES Size is not a mistake. I was hoping to get some feedback from someone with more knowledge about the annotation module in Jetty, so that I don't have to debug using a native profiler. I never tried it on Java programs.
Thanks, Ciprian On Fri, Aug 28, 2015 at 4:17 PM, Christoph Läubrich <[email protected]> wrote: > Maybe it is the just a misleading output of the RES Size? If not all you > can do is attach a native profiler to the JVM process, maybe it resides in > some kind of native code (dll/so)... this is not covered by NMT afaik. > > Am 28.08.2015 13:32, schrieb Ciprian Hacman: > >> Hi Christoph, >> >> I also enabled the detailed data, and the reports are very similar. As I >> said, this extra memory doesn't seem to be tracked by NMT. >> If you look at the summary, it says that it is only 1.1GB of committed >> memory, which mean the RES size should be below that, like when annotations >> are disabled. >> >> Full GC doesn't help, again because this memory is off-heap. >> >> The summaries from the previous emails were generated immediately after >> restarting the Jetty (waited for the server to accept requests). >> This is a production environment, so we restart Jetty only when deploying >> bug fixes. >> >> Ciprian >> >> > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users > -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
