A Case Study of JVM HotSpot Flags | Java.net

世の中カテゴリーの変更を依頼記事元:

weblogs.java.net

2users がブックマークコメント

記事へのコメント1件

注目コメント
新着コメント

yyamano “By default the CMS collector will collect in Perm space but it will not unload classes. If you are frequently loading classes that maybe unloaded in the future then you risk running out of Perm space. For this reason you most likely will need to set CMSClassUnloadingEnabled. Be aware that it will

2014/10/09 リンク

注目コメント算出アルゴリズムの一部にLINEヤフー株式会社の「建設的コメント順位付けモデルAPI」を使用しています

規約違反を報告

いまの話題をアプリでチェック！

バナー広告なし
ミュート機能あり
ダークモード搭載

アプリをダウンロード

A Case Study of JVM HotSpot Flags | Java.net

Just recently I was engaged to assist with an application that wasn’t behaving. The application, ... Just recently I was engaged to assist with an application that wasn’t behaving. The application, running in a 1.7.0_45 JVM, relied heavily on a 3rd party SAAS framework. That vendor provided my client with a list of 26 different JVM flags that should be set. When faced with this long list of flags I couldn’t resist asking why all the flags and why these flags. After all there are more than 700 pro