Re: Memory issue

Posted by Michael Schmid on Oct 03, 2013; 5:46pm
URL: http://imagej.273.s1.nabble.com/Memory-issue-tp5005018p5005032.html

Hi Andrew,

if you have the files on an external disk, what kind of filesystem is it?  If it's a Mac File system (HFS+) that you read on a Windows machine using some third-party software, don't be astonished if it is slow.
(Similarily, NTFS disks from Windows mounted on a Mac with FUSE are very slow).

If it is a Windows filesystem (NTFS, FAT32, exFAT), I would be astonished to hear that it is faster on a Mac/USB 2.0 than on Windows/USB 3.0.  Maybe you can determine the time to copy a few hundred files from the external HD to the internal one on both machines, to see whether reading the files from the HD is the problem?  Then it would be unrelated to ImageJ.

Michael
________________________________________________________________
On Oct 3, 2013, at 19:09, Andrew Riching wrote:

> Hi Curtis,
>
> The format is thousands of individual TIFF files compiled into a folder. I
> collected the images using a Prairie scope (PrairieView software), so I'm
> using the .XML file to open everything. I have not tried a virtual stack,
> but I can try that when I get home tonight. At work, I successfully opened
> the file on a Mac 10.6.8 machine with 8 GB of RAM and a 2 GHz dual core
> processor in 20 minutes. I should also note that the file is on an external
> harddrive. At home I was loading into a USB 3.0 port, but at work I only
> have USB 2.0 ports. In theory, every aspect of my home computer I would
> expect to outperform the lab computer as far as hardware. I should note that
> I have never tried to open the files on a Windows operating system (We have
> XP installed on our lab computers, but XP only recognizes around 3GB of RAM,
> so it's not sufficient for opening these files). I wouldn't think changing
> the operating system should make a difference, so that's why I was trying to
> confirm if there wasn't another setting I needed to change in Windows as
> opposed to Mac in order to change the memory settings.
>
> Thanks,
> Andrew
>
> P.S. Since we're at the same place, would it be easier to try to meet with
> you in person to talk about this issue?

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html