一般来说，为了使线程池的大小更大，您可以上调J vm堆大小设置，但在开始测试时请使用最小内存设置。
JVM heap size Settings generally are adjusted upwards for larger thread pool sizes, but start the testing with minimal memory Settings.
这对JVM堆的大小和性能的影响（尤其在使用持久性会话时）相当大。
The effect on JVM heap sizes and performance (particularly when using persistent sessions) is dramatic.
heaplimit永远不能超过heaptop，也不能低于使用- Xms指定的初始堆大小。
The heaplimit can never exceed heaptop, and can never go below the initial heap size specified using -xms.
每当某个堆超出了其配置的大小时，便可以使用溢出缓冲区来满足实例共享内存区内任何堆的峰值需求。
The overflow buffer is used to satisfy peak memory requirements for any heap in the instance Shared memory region whenever a heap exceeds its configured size.
在另一种形式的跟踪收集器——复制收集器中，堆被分成两个大小相等的半空间，其中一个包含活跃的数据，另一个未使用。
In a copying collector, another form of tracing collector, the heap is divided into two equally sized semi-spaces, one of which contains active data and the other is unused.
堆需求不变的应用程序可以通过使用固定堆大小改进GC暂停时间。
Applications with consistent heap requirements might see GC pause time improvements by using a fixed heap size.
很多开发人员都使用详细GC数据来帮助选择堆的最佳大小。
Many developers use verbose GC data to help choose the best size for the heap.
您可以使用一组从最小到最大的值来调整J vm堆大小设置直到找到最佳设置。
The JVM heap size Settings are adjusted from a minimum to a maximum set of values until the optimal Settings are found.
收集后的空闲堆指标还可以与堆大小结合，共同计算服务器和应用程序所使用的内存工作集(或“内存占用”)。
The free heap after collection metric can also be used in conjunction with the heap size to calculate the working set of memory (or "footprint") being used by the server and application.
利用率和堆大小之间的关系跟应用程序有很大关系，达到一个大致平衡需要使用应用程序和VM参数反复实验。
The relationship between utilization and heap size is highly application dependent, and striking an appropriate balance requires iterative experimentation with the application and VM parameters.
应用程序堆大小参数定义了数据库管理器的一个特定代理或子代理所能使用的私有内存页数。
The application heap size parameter defines the number of private memory pages available to be used by the database manager on behalf of a specific agent or subagent.
固定大小的堆不得小于应用程序的最大内存使用量，以避免出现内存不足的错误。
The fixed heap must be at least as big as the maximum memory usage of the application to avoid out-of-memory errors.
然后，可以使用这个范围内的某个值作为堆的初始大小，这会消除堆增长到稳定状态导致的初始延迟。
You can then use a value from this range as the initial size of the heap, which will prevent the initial delays associated with growing the heap to the steady-state value.
要调优任何应用程序的堆大小，第一步是使用默认堆设置运行应用程序，这允许您测量开箱即用性能。
The first step to tuning the heap size for any application is to run your application using the default heap Settings, which will enable you to gauge the out-of-the-box performance.
使用可变大小堆允许GC仅对堆使用应用程序必需的OS资源。
Using a variable size heap enables the GC to use only the OS resources required by the application for the heap.
使用日志中的堆占用率来决定堆的大小。
Use the heap occupancies in the log to determine how big to make the heap.
堆的大小取决于指定或者默认的最小和最大值以及堆的使用情况。
The size of the heap varies, based on the specified or default heap minimum and maximum sizes, and the usage of the heap.
观察gc之后堆大小的图，可以看到程序内存使用的趋势。
By looking at the graph of heap size after GC, you can see the trend of your program's memory usage.
要正确设置托儿所堆大小，首先需要考虑托儿所收集使用的机制，然后考虑随之出现的二级特征。
To correctly size the nursery, you first need to consider the mechanism that nursery collections use and the secondary characteristics that occur as a result.
stat_heap_sz或统计信息堆大小的数据库配置参数指定了使用RUNSTATS命令收集统计信息中所用堆的最大尺寸。
The stat_heap_sz or the statistics heap size database configuration parameter indicates the maximum size of the heap used in collecting statistics using the RUNSTATS command.
服务器代码在Tomcat6.0.20上运行，配置为使用1,024MB大小的堆，客户机代码使用512 MB大小的堆。
The server code was run on Tomcat 6.0.20, configured to use 1,024mb of heap, with the client code using 512mb of heap.
服务器代码运行在Tomcat6.0.20 上，经配置将使用 1024MB 大小的堆，而客户机代码则使用 512MB 大小的堆。
The server code was run on Tomcat 6.0.20, configured to use 1024MB of heap, with the client code using 512MB of heap. The web service stack versions were
服务器代码运行在Tomcat6.0.20 上，经配置将使用 1024MB 大小的堆，而客户机代码则使用 512MB 大小的堆。
The server code was run on Tomcat 6.0.20, configured to use 1024MB of heap, with the client code using 512MB of heap. The web service stack versions were
应用推荐