Garbage collection can have a big effect on application performance.
垃圾收集对应用程序的性能具有很大影响。
The next line indicates the same information, but denotes a full garbage collection.
第二行指示相同的信息，但表示一个完整的垃圾收集。
Verbose garbage collection is not as verbose as the name suggests.
详细垃圾收集并非像其名称暗示的那样详细。
What percentage of the total available CPU time is spent in garbage collection?
总的可用CPU时间用在垃圾收集上的百分比是多少？
Garbage collection (GC) will usually kick in when a memory allocation failure occurs.
当出现内存分配失败的时候，通常将启动垃圾收集(GC)。
This will give you information on the frequency, timing, and duration of garbage collection operations.
这会使您得到垃圾收集操作的频率、定时和持续时间等信息。
Then, examine the garbage collection logs.
然后，研究垃圾收集日志。
The first line in the example above indicates a garbage collection occurred.
上面示例中的第一行指示发生了一次垃圾收集。
While garbage collection must be tolerated, arduously long pause times are another matter entirely.
尽管必须忍受垃圾收集，但是暂停时间太长完全是另一回事。
How does garbage collection work?
垃圾收集如何工作？
We also recommend that you enable verbose garbage collection tracing.
我们还建议启用详细的垃圾收集跟踪。
The most straightforward garbage collection strategy is reference counting.
最直观的垃圾收集策略是引用计数。
The JVM is effectively paused during the garbage collection run.
在运行垃圾收集期间，JVM实际上会暂停。
Reference objects introduce some additional costs into the garbage collection process.
引用对象给垃圾收集过程带来了一些附加的成本。
From this simplistic definition of garbage collection, you can deduce that the system is not doing any application work while garbage collection is happening.
根据这个简化的垃圾收集定义可以推断出，在执行垃圾收集时系统不会执行任何应用程序工作。
The three most important are garbage collection, managing bad blocks, and wear leveling.
三个最重大的挑战分别是垃圾收集、管理坏块和平均读写。
Next, understand your application's garbage collection requirements and tune the JVM accordingly.
接下来，了解应用程序的垃圾收集需求并相应地调整J VM。
How does the change impact garbage collection?
更改如何影响垃圾收集？
This will increase CPU cycles with garbage collection of UI objects.
这会随着UI对象的垃圾收集而增加CPU周期。
Using garbage collection to simplify memory management for lists.
使用垃圾收集器来简化列表的内存管理。
To understand this, the first thing you need to check is garbage collection.
要理解这一点，首先需要检查的是垃圾收集。
JVM heap size parameters directly influence garbage collection behavior.
jvm堆大小参数将直接影响垃圾收集行为。
Obviously, a lot of garbage collection can really slow down your application.
显然，大量的垃圾收集可以真正减慢应用程序的运行速度。
Either way, your JVM's output will now include the garbage collection information.
无论采用哪种方法，JVM的输出现在都会包含垃圾收集信息。
This provides a good balance of higher garbage collection intervals and lower pause times, which results in a small amount of time spent in garbage collection.
这在较长垃圾收集间隔时间与较短暂停时间之间达到了平衡，从而减少了垃圾收集所花费的时间。
Enable verbose garbage collection logging in your JVM, which will start logging garbage collection activity.
在JVM中启用详细垃圾收集日志记录，这会开始记录垃圾收集活动。
In certain situations, however, garbage collection performance nosedives for no apparent reason.
但是在某些情况下，垃圾收集的性能会莫名其妙地迅速降低。
The LPGC provides garbage collection in parallel to the JVM's work.
LPGC提供与JVM的工作并行的垃圾收集功能。
The LPGC provides garbage collection in parallel to the JVM's work.
LPGC提供与JVM的工作并行的垃圾收集功能。
应用推荐