"However, we also noticed that if your code cache size is not big enough, it may negatively impact your application's performance (i.e., Response Time)."
"Basically it sets the maximum size for the compiler's code cache. In 1.5.0_06 and earlier, the default was 1024MB for Solaris 64-bit and amd64. Now the default is 48MB for Solaris 64-bit, amd64, and -server x86."
"Finally, be warned that options that are specified with -XX are not stable and are not recommended for casual use. These options are subject to change without notice"
Daniel may a bit more conservative than I am about calling this issue closed, but in any case, this has made a noticable difference on our system(s). Many thanks to @viragegroup for pointing this out, what has been hiding in plain sight for ages!
I want to say thank you to all of you. We have tried a lot and at the end we found a solution. Special thank go to viragegroup!
@Chris and @Daniel, you're welcome.
Just wanted to say thank you. You saved our lifes
Our Jboss 7.1.1 server had big performance problems every day. Sometimes a restart was needed every 4 hours under heavy load.
After adding -XX:+TieredCompilation, our server has been running with no problems for 3 weeks now.
Thanks a lot for this. We were puzzled by exactly the same problem for some days. no cpu load nor ram usage but slow performance after some hours. in addition we were not able to load the cpu fully with a simple ab stress test. just after the server start it was no problem. we could get our cpu to nearly 100% but after a few hours later, we were not able to reach more than 20 to 30 %. So maybe this is a good indicator for having this kind of problem, if you can't load your cpu fully.
with TieredCompilation off we have no more performance problems and can always use 100% of our cpu!