3 ms·

Will this help spark performance at all? I remember having to make a lot of GC tweaks in order to get some of the larger jobs to run.

• threeseed 8y ago
  For most ordinary applications I've seen around about 5-10% of the time is spent on GC. Maybe some badly tuned applications would see benefits. If you want an order of magnitude jump in performance need to see if the IBM work on Scala Native version of Spark manifests.
• spricket 8y ago
  It should help performance on almost any JVM app, but much more on large heaps. The GC time is lower and multi-threaded but most importantly the "pause time" is low and nearly constant (based on root set size) The old GC's all scaled pause time roughly linearly with heap size. Apps that created a lot of garbage would have all their threads yielded for large amounts of time. Now, essentially, it doesn't matter how much garbage you create. This is awesome because you used to carefully watch how many allocations you made to avoid bad GC times. Now it doesn't matter. Make as much trash as you want and the GC will deal with it