Dmitri,

Thanks again for you response.


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

  This could be due to the 10 Mb network card you have on this
  machine. See more on this below
I performed an experiment today where we throttled down the network
connection to my 1.8 GHz PC to 10 Mbs. When I attempted to
display the Java applet on my local WinaXe server, even though
-Dsun.java2d.pmoffscreen=false was set, the performance
was just as bad as it was on the HPUX 10.2 box. So it looks like the 10Mbs
isn't sufficient for the current implementation
of Java2D. (By the way, the only Java2D features used in this applet
currently are thick lines a rectangle filled with a
semi-transparent color.)

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.


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

  This is most likely due to one of the following bugs in
  the framebuffer (pgx32) drivers:
    4522502: pgx32 24+8 mode: XShmPutImage has problems with pixels with
MSB set
    4506566: Problem w/ Animator demo on PGX32  (pixmaps problem)
    4517899: black painted selection screens in webstart install on
machines with GFX cards

  Please make sure you have the latest revision of this patch: 109154
  (run 'showrev -p | grep 109154' to check the revision)
  Current revision for Solaris 8 is -15.
Thanks, that patch fixed the black rectangle problem. BTW, the jumbo patch
set distributed with
JDK 1.4.1 for Solaris 8 doesn't include that patch.




  Try to run your app with the following env. variable set:
  J2D_PIXMAPS=shared

  You might want to increase the amount of shared memory
  in the system (by default it's just about 1M, which is way
  to small):
  To change the default settings on Solaris, modify system's settings
  in /etc/system : add, for example, the following lines, then reboot:
  set shmsys:shminfo_shmmax=10000000
  set shmsys:shminfo_shmmni=200
  set shmsys:shminfo_shmseg=150
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 it looks like we're kind of hosed on machines with 10 Mbs ethernet
cards. Do you know of any other tricks to
get the rendering to improve across X such as using less colors, or less
resolution?

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