Dmitri, Thanks again for the response.
> Can you avoid using translucent color? > I don't think thick lines would affect you as much. > (ready to be corrected) We have another "non-fancy" mode where we mimic transparency using fine crosshatching. So we can make do without transparency for now. I'll see if any of the other Java2D features we or OpenMap uses will cause a serious bottleneck. (I know OpenMap tends to be very sluggish across the 10 Mbs connection, but I haven't narrowed down the exact part of the rendering that is creating the slowdown. It responded great over the 100 Mbs connection using the -Dsun.java2d.pmoffscreen=false flag. It doesn't use any transparency features that I know of.) > > One odd thing about this performance issue is that our Dialogs never > paint > > when they are popped once any Java2D call is made. > > You can get some of the widget to show up by scrubbing it with your mouse > > pointer. So even if we could live with the slow > > response, the paint problem in the dialogs shuts us down. > > This is strange and sounds like a bug. If you can create a simple > testcase and send it to me, I'll take a look. Which configuration is > that? Did you see that with 100Mb line? I only see this problem on the 10 Mbs connection, but not the high speed connection. I'll put together a simple test case when I get a chance. > > Simply setting J2D_PIXMAPS didn't fix the performance problem. But > after I > > changed the shared memory > > settings like you suggested, the performance did improve quite a bit. > > Although, it turned out that using > > -Dsun.java2d.pmoffscreen=false without J2D_PIXMAPS was faster for some > > reason. (I tested this by resizing > > a rectangle filled with a semi-transparent color.) > > So were you rendering to the screen or to the offscrreen image? > Note that if you have a swing application, then you're > double-buffered, that means that you're rendering to the offscreen > image. > > If that's the case, then it's possible that turning off the > the acceleration of offscreen images with pmoffscreen=false could > actually help you in this case. > > But in this case you'd probably loose some performance on operations > like scrolling. Our entire application is written using Swing so we definitely need the double-buffering. I turned off double-buffering for the entire application at one point but the flickering and slow redraws of the Swing components made that approach unusable. Thanks again, Rob =========================================================================== 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".
