StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Lots of memory allocated outside Java's heap after upgrading to Java 6u10? Can only be one thing:</p> <p><a href="http://www.oracle.com/technetwork/java/javase/6u10-142936.html" rel="nofollow">Java6 u10 Release Notes</a>: <strong>"New Direct3D Accelerated Rendering Pipeline (...) Enabled by Default"</strong></p> <p>Sun enabled Direct 3D accelerations by default in Java 6u10. This option creates lots of (temporary?) native memory buffers, which are allocated outside the Java Heap. Add the following vm argument to disable it again: </p> <p>-Dsun.java2d.d3d=false </p> <p>Note that this will NOT disable 2D hardware acceleration, just some features that can make use of 3D hardware acceleration. You will see that your Java heap usage will increase by up to 7MB, but that's a good trade-off because you'll save ~100MB(+) of this temporary volatile memory.</p> <p>I did a fair amount of testing within 2 Swing desktop application, on two platforms: </p> <ul> <li>a high-end Intel-i7 with nVidia GTX 260 graphics card,</li> <li>a 3-year laptop with Intel graphics. </li> </ul> <p>On both hardware platforms the option made practically zero subjective difference. (Tests included: scrolling tables, zooming graphical flowsheets, charts, etc.). On the few tests where something was subtly different, disabling d3d counter-intuitively <em>increased</em> performance. I suspect that memory management/bandwidth problems counteracted whatever benefits the d3d accelerated functions were supposed to achieve. (Your mileage may vary!)</p> <p>If you need to do some performance tuning, here's an <a href="http://www.oracle.com/technetwork/java/javase/index-142560.html" rel="nofollow">excellent reference</a> (e.g. "Troubleshooting Java 2D") </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload