Posted by
Albert Cardona on
Apr 04, 2007; 3:55pm
URL: http://imagej.273.s1.nabble.com/memory-limit-and-the-64-bit-era-tp3699808p3699809.html
Michael,
> (browsing of *large* datasets acquired by 5D microscopy is still one of
> the major limitations in the life-sciences)
In my experience having all images opened at once doesn't help much. What does
help is virtualization: either purely virtual stacks like those offered by the
virtual stack opener plugin, or a virtualization layer with a fifo on-demand
reloading cache like TrakEM2.
I don't have experience with 5D, but for 4D we regularly open 15.000 16-bit
images (from SPIM microscope) with the Virtual Stack Opener, and then apply the
4D hypervolume browser on it without problems. Scrolling through the stack is
fast, almost unnoticeable (even when the files physically live on a
gigabit-networked remote file server). ImageJ doesn't need more than a few
hundred megabytes to handle the above seamlessly.
As for internal ImageJ-related 64-bit limitations: I am not aware of any. Only
if single images are bigger than the 32-bit limit, or more than such 32-bit
images are open, may you see strange behaviours.
The JVM crashing after allocating -Xmx3000 for it and then just opening the
'About ImageJ' sounds to me like a JVM problem, not an ImageJ problem.
Albert
--------------------------------------------------------------------
This message was sent using Webmail@INI:
https://webmail.ini.ethz.ch