When can Graphics2D.fill () work in SWT 10 times slower?

Question

I will investigate the problem when the Piccolo2Dgraphics are much slower when inside the bridge SWT.

Finally, I found that code that runs a lot slower is a method call Graphics2D.fill(). In the case of the SWT bridge, it works 10 times slower than in the usual Swing.

The likely cause is the clipping region.

What are other possible causes?

And as you can see, what is the reason for clipping? The result Graphics2D.getClipBounds()is the same in both cases, but it is documented as the user's clipping region. Can I see the clipping area of ​​the device?

Answer 1

SWT , Swing, . , ( ) Java ( ). "" ( ) , JVM , , (,...).

Swing " " , , JIT, .

, SWT , , .., Java .

, Piccolo2D , , SWT: - (