Experimental Physics and
Industrial Control System

"J. Lewis Muir" <[email protected]> · Sun, 19 Sep 2010 16:00:11 -0500

On 9/17/10 11:57 PM, Szalata, Zenon M. wrote:
> Hi Kay,
> In spite of your elaborate argument, quite convincing at that, I am
> not convinced that there is no problem.  It may be that all is working
> as designed, but then it was designed poorly.  Whether it is java ,
> eclipse, or CSS that is falling short, I can't tell.
> I am not convinced that I should not expect to display a 4 MB image at
> 6 or 7 Hz rate on a machine with 3 GB of physical memory without
> generating errors.  This is actually a bit absurd.  Image size is not
> likely to get smaller.  It would be nice if a 4 MB image could stay 4
> MB until it is painted.  On Windows XP, I can display these images at
> 30+ Hz using the software provided by the camera maker.
> Anyway, presently the image rate is limited by the Ethernet adapter
> not being setup for jumbo frames.  These cameras will be used to
> monitor images along the beam line at 10 or 30 Hz when the hardware
> and software goes into production.  Presently I am testing these
> cameras in 8 bit Mono but they are capable of 16 bit color, so the
> volume of data will increase.  I understand that 8 bit or 16 bit is
> all the same for java.
> I see that edm video widget outperforms CSS/BOY intensity graph and I
> hate to think that I should disqualify CSS/BOY due to poor
> performance.

Hi, Zen.

Your email doesn't include what the error messages were, so it's hard to
diagnose.

Did you try Kate's suggestion of increasing the amount of memory
available to your Java virtual machine?  For a Java application running
in a Sun (now Oracle) Java VM, you can specify the maximum heap size
with the -Xmx option to the Java VM when you start it.  For example, to
execute a class named ImageViewer with the maximum VM heap size set to 1 GB:

  java -Xmx1024m ImageViewer

I don't know how CSS BOY is started, but I would expect you could
specify options passed to the Java VM somewhere.

If there's no bug in CSS BOY related to this, and if increasing the
maximum heap size doesn't help, then perhaps the Java VM is still
running out of heap space.  If so, then it might be that CSS BOY needs
an optimization for this case.  For example, rather than creating
objects representing images and forgetting them, waiting for the garbage
collector to reclaim them in the future, one could keep a pool of image
objects and reuse them.  But this is all speculation since I haven't
looked at the code and don't know what's actually happening.

Lewis

-- 
J. Lewis Muir
Software Engineer
IMCA-CAT

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System