java虚拟机的内存设置(Memory settings for the Java virtual machine).doc

java虚拟机的内存设置(Memory settings for the Java virtual machine).doc

  1. 1、本文档共8页,可阅读全部内容。
  2. 2、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
  3. 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  4. 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
java虚拟机的内存设置(Memory settings for the Java virtual machine)

java虚拟机的内存设置(Memory settings for the Java virtual machine) Memory settings for the Java virtual machine Basic concept: PermGen space: the full name is Permanent Generation space., that is, the permanent storage area used to store Class and Meta information, and Class is placed into the area when it is Load Heap space: store Instance. GC (Garbage Collection) should not clean PermGen space So if your APP will be a lot of CLASS, PermGen space errors are most likely to happen to you, LOAD Java Heap is divided into 3 areas 1.Young 2.Old 3.Permanent Young saves objects that have just been instantiated. When the area is filled, GC moves the object to the Old area. The Permanent section is responsible for saving reflection objects, and this area is not discussed in this article. The Heap allocation of JVM can be set using the -X parameter, -Xms Initial Heap size -Xmx Java heap maximum -Xmn Heap generation size of young JVM has 2 GC threads The first thread is responsible for retrieving the Young zone of the Heap The second thread, when Heap is insufficient, traverses the Heap and upgrades the Young zone to the Older zone The size of the Older zone is equal to -Xmx minus -Xmn, and the value of the -Xms cannot be set too large because the second threads are forced to run, which reduces the performance of the JVM. Why do some programs happen frequently, GC? For the following reasons: 1., System.gc () or Runtime.gc () is invoked within the program. 2. some middleware software calls its own GC method, which needs to set parameters to prohibit these GC. The Heap of 3.Java is too small, and generally the default Heap values are small. 4. frequently instantiate objects, Release objects, at this point to save and reuse objects, such as using StringBuffer () and String (). If you find that the remaining space of Heap will be 50% of the total space after each GC, this means that your Heap is in a healthy state Many Server side Java programs are best to have 65% of the space left after

您可能关注的文档

文档评论(0)

jgx3536 + 关注
实名认证
内容提供者

该用户很懒,什么也没介绍

版权声明书
用户编号:6111134150000003

1亿VIP精品文档

相关文档