如果内存使用减少，那么系统容量或性能就能够得到提升，从而允许增加会话或减少垃圾收集时间。
If memory usage can be reduced, then the system's capacity or performance can be improved, allowing more sessions or less time spent garbage collecting.
总的可用CPU时间用在垃圾收集上的百分比是多少？
What percentage of the total available CPU time is spent in garbage collection?
尽管必须忍受垃圾收集，但是暂停时间太长完全是另一回事。
While garbage collection must be tolerated, arduously long pause times are another matter entirely.
垃圾收集停顿时间是任何线程遇到的最显著的延迟。
The garbage collection pause times are the most significant delays any threads encounter.
但是，您应该将托儿所堆大小固定为一个较大的值，以最小化垃圾收集花费的时间，增强保留区堆，使其根据占用率重置自身大小，从而提高弹性。
You should, however, fix the nursery size at a large value to minimise time spent in garbage collection, and enable the tenured heap to resize itself according to occupancy to build in resilience.
当然，理论上说，这个城市并没有变小，有着几乎与以前一样的养路需求，街区照明，垃圾收集以及紧急服务响应时间。
Yet physically, of course, the city remains the same size, imposing most of the same requirements of road maintenance, street lighting, rubbish collection and emergency-service response times.
您可以通过查看摘要确认这一点，摘要显示6.2%的应用程序时间花费在垃圾收集上。
You can confirm this by looking at the summary, which shows 6.2% of the application's time is spent in garbage collection.
随着托儿所空间大小和托儿所收集之间的时间间隔增加，需要复制的数据量通常会随之减少，垃圾收集的开销也会随之降低。
As the nursery size is expanded and the time between nursery collects increases, you do less copying on average, and the overhead of garbage collection drops.
从第一个图形中，您可以看到应用程序运行了大约100秒，所以进行垃圾收集花费了该时间的0.3%。
From the first graph, you see the application had been running for about 100 seconds, so 0.3% of that time had been spent doing garbage collection.
遗憾的是，增加堆大小的一个缺点是查找和处理需要垃圾收集的对象所需的时间也会随之增加。
Unfortunately, an associated downside to increased heap size is a corresponding increase in the amount of time needed to find and process objects that should be garbage collected.
事实上，随着托儿所空间增大，垃圾收集所需的总时间会随之降低。
In effect, as the nursery is made larger, the overall time spent in garbage collection drops.
根据您的响应时间需求，可能无法容忍JVM的垃圾收集开销达到12%。
Depending on your response time requirements, you might not be able to tolerate a JVM running at 12% garbage collection overhead.
用于垃圾收集的标记和清扫阶段的GC暂停时间基于堆上的活动对象的数量。
The time spent in GC pauses for the mark and sweep phases of a garbage collection are based on the number of live objects on the heap.
根据程序的分配速度，系统试图预测下次需要执行垃圾收集的时间。
Based on the program's allocation rate, the system attempts to predict when the next garbage collection will be required.
垃圾收集日志还会指出发生垃圾收集的时间以及垃圾收集花费的时间。
The garbage collection logs also indicate the time at which the collection appears and the length of time the garbage collection takes.
如果用-verbose：gc开关运行评测，您可以看到在垃圾收集上耗费了多少时间，并相应地调整您的计时数据。
If you run your benchmarks with -verbose: gc, you can see how much time was spent in garbage collection and adjust your timing data accordingly.
对象高速缓存和合用：应用程序服务器自动在服务器级合用无状态会话bean，这减少了花在对象创建和垃圾收集上的时间。
Object caching and pooling: the application server automatically pools stateless session beans at the server level, reducing the amount of time spent in object creation and garbage collection.
rpgcontrol支持三个选项，通过引用npsrpgmin和npsrpgmax选项控制执行垃圾收集的时间。
The rpgcontrol supports three options and controls when garbage collection is performed with reference to the npsrpgmin and npsrpgmax options.
根据这些时间戳，还可以计算出系统在垃圾收集方面花费的时间百分比，可以用这个指标比较各种JVM设置。
From these timestamps, you can also calculate the percent of time that the system spends in garbage collection, which you can use to compare various JVM Settings.
如果响应时间比最高流量更重要，这个垃圾收集器可能是一个不错的选择。
If response time is more important than highest possible throughput, this garbage collector might be a good choice.
如果系统中存在正在排队等候的任务，那么系统的响应时间可能会受到排队时间的控制，而不是垃圾收集停顿时间。
In any system where work is queuing up, the response time of the system is likely to be dominated by the queueing time, rather than any garbage collection pauses.
这会使您得到垃圾收集操作的频率、定时和持续时间等信息。
This will give you information on the frequency, timing, and duration of garbage collection operations.
更好一些的话，您可以长时间运行您的程序，这可以保证触发许多垃圾收集，从而更精确地分摊垃圾收集的成本。
Even better, you can run your program for a long, long time, ensuring that you trigger many garbage collections, more accurately amortizing the allocation and garbage collection cost.
您可以执行的最简单的调整就是指定一个策略并告诉垃圾收集器是吞吐量重要还是暂停时间最重要。
The simplest tuning you can do is to specify a policy and tell the garbage collector whether throughput or pause times are most important.
了解您的系统将多少时间花费在垃圾收集上，这是很有必要的，但是将过多的时间花费在垃圾收集上将会对系统的性能产生怎样的影响呢？
Knowing how much time your system spends in GC is all well and good, but how does more time spent doing garbage collection actually affect the performance of your system?
在较小的堆中，当必须频繁收集垃圾时，停顿时间对应用程序响应时间的影响比在较大堆中不频繁收集时的影响更大。
In smaller heaps, when garbage must be collected very frequently, the pause times have more of an effect on application response times than they do in very large heaps, with infrequent collections.
评估GC的性能影响时，需要检查的最重要的项目是暂停时间和开销：用于进行垃圾收集而不是执行应用程序工作的时间的比例。
When assessing GC's performance effects, the most important items to check are the pause times and the overhead: the proportion of time spent garbage collecting instead of doing application work.
另一方面，传统的垃圾收集器可导致长时间的延迟，而应用程序编程人员几乎不可能预测出这一时间。
On the other hand, traditional garbage collectors can introduce long delays at times that are virtually impossible for the application programmer to predict.
例如，如果正在进行垃圾收集或传入队列中有大量的请求，那么处理请求的时间可能稍长些。
For example, if garbage collection is underway or if there are lots of requests in the incoming queue, requests may take longer to be processed.
优化性能的一个明显方法是选择能够最小化垃圾收集停顿时间带来的消极影响的GC策略。
One obvious way to optimize application performance is to choose a GC policy that minimizes any negative impact of garbage collection pauses.
应用推荐