blocks|key|586569|text|使用的总虚拟内存是最大堆%2B线程堆栈%2B直接内存%2B+perm+gen+%2B共享库的总和。这永远不会缩小。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|586570|实际使用的主内存取决于占用了多少虚拟内存。共享库是共享的，因此拥有多个JVM不会导致内存加倍等等。|586571|JVM从不向操作系统释放内存，但是如果很长一段时间没有使用主内存，则可以在需要时将内存交换出去。|586572|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The total virtual memory used is the sum of the maximum heap + thread stacks + direct memory + perm gen + share libraries. This never shrinks.

The actual main memory used depends on how much of the virtual memory has been occupied. Shared libraries are shared so having multiple JVMs won't result in this memory doubling etc.

The JVM never releases memory to the OS, however if main memory is not used for a long time it can be swapped out if this is need.

blocks|key|2187295|text|实际的内存消耗比用Xmx等设置的内存更多，这是正常的。java将为其他事情分配内存，包括每个线程的堆栈。VM的总内存消耗超过-Xmx的值并不少见。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2187296|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The actual memory consumption is more than what what you set with Xmx etc, that's normal.
"java will allocate memory for other things, including a stack for each thread. It is not unusual for the total memory consumption of the VM to exceed the value of -Xmx."

blocks|key|2187344|text|参数-Xmx1600m+-Xms1600m告诉JVM至少分配1600+at内存，最多分配1600+at内存。因此JVM应该在启动时分配1600+it，并且永远不要释放它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2187345|如果您希望JVM将内存释放回操作系统，那么-Xms应该很低，您可能需要在新的G1垃圾收集器中使用Java1.7。/wp/?P=14。|2187346|使用MacOSX10.8和Java1.7和-Xms32m+-Xmx256m+-XX:%2BUseG1GC+-XX:MinHeapFreeRatio=5+-XX:MaxHeapFreeRatio=10，在运行System.gc()之后，将将内存释放回操作系统。|2187347|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The paramaters -Xmx1600m -Xms1600m tells the JVM to allocate 1600MB of memory at minimum and 1600MB of memory at maximum. So the JVM should allocate 1600MB on start up and the never release it.

If you want the JVM to release memory back to the OS then the -Xms should be as low, and you probably have to use Java 1.7 with the new G1 garbage collector. stefankrause.net/wp/?p=14. 

Using Mac OS X 10.8 and Java 1.7 with -Xms32m -Xmx256m -XX:+UseG1GC -XX:MinHeapFreeRatio=5 -XX:MaxHeapFreeRatio=10 the memory is release back to the OS after a System.gc() is run.

blocks|key|586602|text|在堆中，Java虚拟机(+Java+Virtual，JVM)存储Java应用程序创建的所有对象，例如使用“新”操作符。Java垃圾收集器(+gc+)可以在逻辑上将堆划分为不同的区域，这样gc可以更快地识别可以被移除的对象。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|586603|新对象的内存是在运行时在堆上分配的。实例变量存在于声明它们的对象中。|586604|堆栈是存储方法调用和局部变量的地方。如果一个方法被调用，那么它的堆栈帧就会被放到调用堆栈的顶部。堆栈帧保存方法的状态，包括正在执行的代码行和所有局部变量的值。堆栈顶部的方法始终是该堆栈的当前运行方法。线程有自己的调用堆栈。|586605|如前所述，Java对象是在堆中创建的。编程语言没有提供让程序员决定是否应该在堆栈中生成对象的可能性。但是在某些情况下，需要在堆栈上分配对象，因为堆栈上的内存分配比堆中的内存分配更便宜，堆栈上的去分配是免费的，堆栈由运行时有效地管理。|586606|因此，JVM使用内部转义分析来检查对象是否仅与线程或方法一起使用。如果JVM确定了这一点，它可能决定在堆栈上创建对象，从而提高Java程序的性能。(http://www.ibm.com/developerworks/java/library/j-nativememory-linux/)|offset|length|586607|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ibm.com/developerworks/java/library/j-nativememory-linux/^0|0|0|0|0|22|1W|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$J|Y|K|Z|1|10]]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

In the heap the Java Virtual Machine (JVM) stores all objects created by the Java application, e.g. by using the "new" operator. The Java garbage collector (gc) can logically separate the heap into different areas, so that the gc can faster identify objects which can get removed

The memory for new objects is allocated on the heap at run time. Instance variables live inside the object in which they are declared.

Stack is where the method invocations and the local variables are stored. If a method is called then its stack frame is put onto the top of the call stack. The stack frame holds the state of the method including which line of code is executing and the values of all local variables. The method at the top of the stack is always the current running method for that stack. Threads have their own call stack.

As said earlier in Java objects are created in the heap. The programming language does not offer the possibility to let the programmer decide if an objects should be generated in the stack. But in certain cases it would be desirable to allocate an object on the stack, as the memory allocation on the stack is cheaper then the memory allocation in the heap, deallocation on the stack is free and the stack is efficiently managed by the runtime.

The JVM uses therefore internally escape analysis to check if an object is used only with a thread or method. If the JVM identify this it may decide to create the object on the stack, increasing performance of the Java program.
(http://www.ibm.com/developerworks/java/library/j-nativememory-linux/)

I have read through this <a href="https://stackoverflow.com/questions/4893192/process-memory-vs-heap-jvm">Process Memory Vs Heap -- JVM</a> 
 and i have the same problem. 

The jvm process memory usage keeps increasing and never shrinks.I checked by doing a top on the linux server. The application is scheduling jobs to a cluster ( Using Quartz + Sun Java DRMAA API )

The java heap space is staying within the limits during the application life cycle but the jvm process is showing a steady climb in memory usage and never coming down. 

Is this a memory leak ? If so , why is heap space being within the limits. Can someone explain this.

UPDATE: I have -Xmx1600m -Xms1600m when i track through jconsole i can see the heap space well within this limit aroung 450m but the top command shows the process is using more than 900m.

JVM Process vs JVM Heap memory usage

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我读过这个，我也有同样的问题。jvm进程内存使用量一直在增加，而且从未收缩。我在linux服务器上做了一个顶部检查。应用程序正在将作业调度到集群(使用Quartz +)java堆空间在应用程序生命周期期间保持在限制范围内，但是jvm进程显示内存使用量正在稳步上升，并且永远不会下降。这是内存泄漏吗？如果是这样的话，为什么堆空间在限制之内。有人能解释一下吗。更新：，我有-Xmx1600m -Xms16

问JVM进程与JVM堆内存的使用
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JVM进程与JVM堆内存的使用EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JVM进程与JVM堆内存的使用
EN