Memory allocation behaviour with Java 1.8 in Tomcat 6 and Tomcat 8

六眼飞鱼酱① 提交于 2019-12-05 01:01:27

This is eden space, not the tenured space. So, that alone is good news.

But that step of memory appears to be tomcat8 allocating something right away after a young GC. Could it be some 'balloon' technique? (allocating a large weakly referenced buffer to 'deflate' rapidly to ensure some room in case of memory pressure). It may hide in NIO connectors too, as in the 'oomParachute' parameter (1 MB by default, but is it per httpprocessor thread? If you had 200 min threads, that would match the 200 MB seen).

I will only suggest that you can drill into the changelog to find new thing or changes that you might think they implemented wastefully like such balloon mechanism.

ALSO: you should run the tomcat6 in your jdk8 to see if it is really tomcat8 at fault. The eden space could be made larger, just in case the G1GC is so aggressive that it feels obligated to GC when a mere 200MB is used.

Thank you all guys for your time. In the end, the problem is a bug in tomcat 8.0_23. Using Javosize, i saw a thread consuming almost all CPU time:

Looking on the internet i found this Tomcat AJP Bug

In adittion, i've tested tomcat 8.0_32 and that Poller thread does not even exist so problem solved.

Regards

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!