You can also invoke the JVM's garbage collector (GC).
还可以调用JVM的垃圾收集器(GC)。
This memory cannot be released by the garbage collector.
这个内存不能被垃圾收集器释放。
As of Lua 5.1, the garbage collector works incrementally.
在Lua 5.1中,垃圾收集器是以增量方式工作的。
The garbage collector interacts closely with the class loader.
垃圾收集器与类装入器的交互很密切。
This is also why the garbage collector is called Garbage-First.
这也是为什么该垃圾收集器叫做Garbage - First的原因。
Typically a garbage collector is optimised for one or the other.
垃圾收集器通常两者只能顾其一。
There are also many interesting statistics about the garbage collector itself.
还有许多关于垃圾收集器本身的有趣的统计信息。
Next, I added, then deleted four forms and again invoked the garbage collector.
随后,我添加了四个窗体,然后又将它们删除,并再次调用了垃圾收集器。
Probably. He claims his next move was going to be phoning the garbage collector.
他宣称下一步行动就是给垃圾回收员打电话。
The performance improvements are mainly due to the new lazy sweep garbage collector.
性能的提升主要归功于新的懒惰式扫描(Lazy Sweep)垃圾回收器。
This can occur if the program ends prior to the garbage collector freeing the object.
如果程序在垃圾收集器释放对象之前结束,这种情况就可能会出现。
Memory: For tracking activity against the various heaps in the JVM's garbage collector.
Memory:在JVM垃圾收集器中针对各个堆跟踪活动。
The memory management and garbage collector is to be found in the separate MMgc project.
内存管理和垃圾收集器属于MMgc子项目。
Note the periodic dips corresponding to time quanta where the garbage collector is active.
注意垃圾收集器活动状态下对应于时间量子的周期性下降。
The V8 garbage collector reclaims memory used by objects that can never again be accessed.
V8的垃圾收集器将把不再使用的对象的内存回收掉。
Using garbage collection can be easy or difficult depending on the garbage collector in use.
使用垃圾收集器可能使这些过程变得简单,但也可能使它们变得困难,这要取决于所使用的垃圾收集器。
If the garbage collector discovers an object that is weakly reachable, the following occurs.
如果垃圾收集器发现了弱可及对象,就会出现下列情况。
The garbage collector already does a lot of autonomic tuning to try to optimize its performance.
垃圾收集器为了优化其性能已经执行了很多自动调整。
Lazy sweeping improves the response time of the garbage collector and increases its throughput.
懒惰式扫描缩短了垃圾回收器的响应时间,同时还增加了吞吐量。
It can be scheduled when convenient by the JVM and any impact of the garbage collector is immaterial.
JVM可能在任何方便的时候调度它们,垃圾回收产生的影响也是微不足道的。
I assume most of you are more interested in using a garbage collector than implementing one yourself.
我假设绝大多数人对于使用垃圾收集感兴趣,而不想自己实现一个。
It completes its work when the NHRTs are waiting for more work and the garbage collector is inactive.
在NHRT等待更多工作、垃圾收集器不活动时,它将完成这一工作。
Consider the possibility that the garbage collector may never even run during an application's lifetime.
完全有这样的可能,垃圾收集器在应用程序的生存期内可能始终不会运行。
The garbage collector identifies objects that are no longer referenced and reclaim the unused memory.
垃圾回收器可以识别出不再被引用的对象,并回收空闲出的内存。
If there were, the garbage collector would ship with that configuration, and tuning would be unnecessary.
如果有的话,垃圾收集器将提供该配置,那么调整就没有必要了。
This way, the garbage collector will obtain more breathing space, decreasing the probability of a full GC.
通过这种方式,垃圾收集器将获得更多空间并减少完全GC的可能性。
At this point, the JVM will first attempt to make more memory available by invoking the garbage collector.
当可用内存不能满足需求时,JVM将首先尝试通过调用垃圾收集来释放出更多的可用内存。
This means improving the garbage collector, optimizing generated code, and improving the core libraries.
这就要改进其垃圾回收器,优化生成的代码,并改进其核心库。
This can improve application performance by avoiding the garbage collector unnecessarily shrinking the heap.
这可以避免垃圾收集器对堆进行不必要的收缩,从而改善应用程序性能。
Pooling is quite simple: an object is reused instead of allowing it to be reclaimed by the garbage collector.
池机制相当简单:对象被重新使用,而不是让它被垃圾回收器回收。
应用推荐