> There still seems to be a fair number of > unaccelerated calls, like > MaskFills (fills of antialiased shapes), MaskBlits > (AA shape filled > with gradient), and BI to BI blits.
Hi, Dmitri Thanks for looking into this. The advice on not setting AA mode prior to using operations that don't care about it (such as filling a rectangle, shape or gradient) is a very valuable one. Is this mentioned anywhere in the tutorials / javadoc? Is this implementation detail for Sun VM? Can this be handled in the core by ignoring the AA mode on operations that produce exactly the same results with or without AA turned on? In addition, i wonder what your thoughts are on Nimbus performance on my specific card (the one with acceleration). While in pure software Nimbus is twice as fast as Substance, on that card the usage of volatile images and accelerated loops seems to hurt Nimbus rather badly (instead of boosting it by 30-80% as your internal benchmark suggests). What does your internal benchmark do? Does it just run a sequence of Java2D operations, or is it a real app being tested? I would suggest such a heavy app as Netbeans or IntelliJ IDEA for a "real" test of performance gains on D3D pipeline. The last question - how can i look at the output of sun.java2d.trace=count and understand how it maps back to the Java2D APIs on Graphics and Graphics2D? How do i read something like "sun.java2d.loops.Blit::Blit(IntRgb, SrcNoEa, IntArgbPre)" or "sun.java2d.loops.MaskBlit::MaskBlit(IntArgbPre, SrcOver, IntArgbPre)"? Thanks for your help Kirill [Message sent by forum member 'kirillcool' (kirillcool)] http://forums.java.net/jive/thread.jspa?messageID=271749 =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA2D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
