Hello Dmitri (and all), Well, it's 3 weeks later and we've finally had some success with this. We have a fairly simple Swing application and a more complex imaging app that we are hoping to run over a long-line X windows session. Running on 1.4, both applications are unusably slow, for example 20 seconds to scroll down in a JScrollPane. Running on 1.5, we did see a significant speed boost, but it was still unusable, e.g. 6 seconds to scroll down. (I admit that "unusable" is a subjective measure.)
Then we enabled the XAWT toolkit as you explained below. The engineer doing the tests didn't see any improvement at first but it turned out he was still running 1.4, which fits perfectly with the explanation that XAWT is new for Java 5.0. Once he correctly used Java 5.0, he saw a HUGE performance improvement in the simple Swing app... but sadly the more complex app is still unusable. Our base app has a JDesktopPane with JInternalFrames, however those components don't even play into the performance testing because the speed was bad just with menubar selection. The JDesktopPane is visible when the app is first opened, and JInternalFrames are created when an image is loaded. Other than the JDesktopPane, the app has a JTree, a JMenuBar, and a JToolbar with about 10 toolbar JButtons in it, as well as a JTextField and one or two JComboBoxes. There aren't any fancy dynamic controls, nothing is animated. We do some advanced custom blitting of the image windows and there is transparency involved in the image windows, BUT that's only when there is actually an image loaded. It seems like the basic Swing components at least should perform well. I'm trying to think of what could cause this application to lose the performance improvements of XAWT. Do you have any ideas? Is there any possibility that we're doing something programmatically that would disable the XAWT toolkit up front? Is there something we can do to verify that XAWT is being used? Anything we can learn from a CTRL-Break thread dump? thanks! Mike > -----Original Message----- > From: Discussion list for Java 2D API > [mailto:[EMAIL PROTECTED] On Behalf Of Dmitri Trembovetski > Sent: Friday, November 03, 2006 5:58 PM > To: [EMAIL PROTECTED] > Subject: Re: [JAVA2D] java2d and X sessions > > > Hi Mike, > > On Fri, Nov 03, 2006 at 05:10:03PM -0500, Nidel, Mike wrote: > > > Try running on 5.0 with the XAWT instead > > > the motif toolkit: > > > AWT_TOOLKIT=XToolkit java YourApp > > > (or you can set a -D property for the default toolkit). > > > > > > I don't quite follow how I invoke my app, can i just do > > > > java -Djava.some.property=XToolkit MyApp ... > > > > or is AWT_TOOLKIT a shell variable, or what? > > Here's more information: > http://java.sun.com/j2se/1.5.0/docs/guide/awt/1.5/xawt.html > > > > Also, does your application do any kind of complex rendering, > > > like antialiased rendering or alpha compositing > (translucent images > > > , etc)? > > > > > > If so, you might want to set this property: > > > -Dsun.java2d.pmoffscreen=false > > > It might help. > > > > > > no, the simple application we're testing is just a swing > app > that has various components but nothing fancy. Not > even any > custom components, just basic Swing layouts. > > > However, it's very handy to know this property. What does > it > do, is there an API doc on it? > > > https://java.sun.com/javase/6/docs/technotes/guides/2d/flags.h tml#pmoffscreen Thanks, Dmitri ======================================================================== === 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". =========================================================================== 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".
