We have been evaluating the speed of Java graphics with a simple test case
that simply reads in a file with polylines in it and then outputing them in a
tight loop. We discovered that it was rather slow. We investigated the
process of putting the graphics to the screen through AWT, and found that the
main reason that it is slow is that for each call to polyline (which ends up
at the native function awtGraphics::polyline in awt_graphics.cpp) a call to
the inline method GetDC causes the clipping rectangle to get set in the DC,
unless the Graphis object is set up not to clip.
that simply reads in a file with polylines in it and then outputing them in a
tight loop. We discovered that it was rather slow. We investigated the
process of putting the graphics to the screen through AWT, and found that the
main reason that it is slow is that for each call to polyline (which ends up
at the native function awtGraphics::polyline in awt_graphics.cpp) a call to
the inline method GetDC causes the clipping rectangle to get set in the DC,
unless the Graphis object is set up not to clip.
- duplicates
-
JDK-4128431 win32: awt_Graphics.cpp sets the clip region too often, reducing performance
-
- Closed
-
- relates to
-
-
- Closed
-