Dmitri,

Thanks for your response.


>  > appletviewer -J-Dsun.java2d.pmoffscreen=false
>  >
>  > This appears to solve the performance problem, when displaying remotely on
>  > newer X servers
>  > like WinaXe or Linux or Solaris X-Server, but unfortunately not on the
> HPUX
>  > 10.2 box.
>
>   Does this mean that it still runs slow when displaying remotely to a
>   HP X server, or that you see some rendering artifacts?

The performance is slow on the HPUX X server when using any Java2D
capability. It also runs
slowly when we don't use Java2D but still use the Java runtime parameter:
-Dsun.java2d.pmoffscreen=false.
If we don't use this parameter or Java2D then the performance of the Swing
components is quite acceptable
on the HPUX X server.


>  > (There are some black rectangles that pop up every so often even with the
>  > newer servers though.)
>
>   Could you please describe in more details the problem you're seeing
>   with the newer X servers?
>
>   Also, please list the exact configuration (client and server OS's,
>   whether they're fully patched, the framebuffer on the X server
>   machine).

The Sun box where the Java client is running is a fully patched 800 Mhz
Solaris 8 Netra T4. I'm not sure what graphics card it
has, but after perusing the device directory we saw something called a TSI
gfxp.

The PC that I'm running WinaXe server on is a Dell Dimension 8200, 1.8 GHz
running Windows 2000.
The HPUX 743 box is running HPUX 10.2. I'm not sure about the patch level.
I'm looking into it.

Ironically, the solid (black or green) boxes are showing up on the Solaris
box (acting as client and server)
  if I use the local console when use -Dsun.java2d.pmoffscreen=false.
These boxes tend to show up in the toolbar and text entry fields.
Furthermore, it appears that even though I'm running the
application locally that the performance is poor when using Java2D
functions (like transparency) without setting
-Dsun.java2d.pmoffscreen=false! The performance is much better with the
flag being set to false.

The solid boxes don't show up on the Linux or WinaXe servers.

>   A testcase would be really useful.

I'll see if I can create a simple test case.

>   Also, what's your network bandwidth?

The network bandwidth is 100 Mb in general. The HPUX box has a 10 Mb
ethernet card.  Everybody else has 100 Mb cards.

>  > We would very much like to use Java2D capability for our application.
> (We'd
>  > like to use OpenMap components that utilize Java2D and features such as
>  > transparency, thick lines, transformations, etc. in our own application.)
>  > Is there any way to accomplish this with JDK 1.4.1? Will this issue be
>  > resolved any time within the next two months?
>
>   Unfortunately, there isn't much we can do about the performance
>   problem on remote X when using 2D rendering which includes reading
>   from the destinatuion surface (translucency effects, antialiasing).

That's unfortunate since it really hamstrings our development and will
disappoint our customer.
I know that applications using OpenGL have been able to be
displayed over the network efficiently. (For instance with Exceed3D or with
IRIX systems.)
These applications use transparency, shading, antialiasing and such. Maybe
there are some lessons there.

>   As for the rendering artifacts you're seeing, we need more info
>   from you.
>
>   Also, we probably won't be able to help with the issues with HP X
>   server, you might want to contact HP regarding this.

The Java2D performance problem is well documented in bug reports.  I don't
believe it is a problem associated only with HPUX X servers, but I will
look into it.

Thanks,

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".

Reply via email to