Revision as of 18:29, 18 February 2010 by Tpavek (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)

Can I eliminate pauses caused by garbage collection?

If you find the garbage collection pauses too intrusive you can try switching to a different garbage collection algorithm.

You can set one of the following switches in etc/netbeans.conf or on the command-line when you start Netbeans:

  • -J-XX:+UseConcMarkSweepGC or -J-XX:+UseParNewGC
  • this switch causes the JVM to use different algorithms for major garbage collection events (also for minor collections, if run on a multiprocessor workstation), ones which do not "stop the world" for the entire garbage collection process. If you are using the PermSize switch, you should also use -J-XX:+CMSClassUnloadingEnabled and -J-XX:+CMSPermGenSweepingEnabled so that class unloading is enabled (it isn't by default when using this collector).
  • -J-XX:+UseParallelGC
  • some tests have shown that, at least on systems fairly well equipped with memory, the durations of minor garbage collections is halved when using this collection algorithm, on uniprocessor systems. Note that this is paradoxical - this collector is designed to work best on multiprocessor systems with gigabyte heaps. No data is available on its effect on major garbage collections. Note: this collector is mutually exclusive with -J-XX:+UseConcMarkSweepGC.

  Applies to: NetBeans 4.x and newer
  Platforms: All
  See also: Tuning JVM Switches for performance
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo