not enough VM

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

not enough VM

Thoralf Seewald
Dear ImageJ users,
I am trying to increase the memory for imageJ. I need around 3.8 GB for processing plug-ins I want to go through. But after the change in the command line greater than 2600mb the software does not start anymore with the notice, that there is not enough Virtual Memory.

I am usin a 2x3.2 GHz Intel Xeon with Fedora Core 5 (32bit).

I would great appreciate an idea or help with my little problem.

Thank you in advance,


Thoralf Seewald.

--
Hightech Research Center Basel (HFZ)
_______________________________

Mail:  [hidden email]
       [hidden email]
Fon:   +49 /  30 - 206.87.602
Mobil: +49 / 176 - 222.02.507
       +41 /  76 - 50.55.798
_______________________________
Reply | Threaded
Open this post in threaded view
|

Re: not enough VM

Duane and Julie
Thoralf,

You got 2600MB?  Consider yourself lucky.  With a 32 bit JVM (which  
is what most of us have) you max out around 1500MB.

The bigger question, though, is why do you need 3.8GB?  That equates  
to a VERY large image, or a large stack of large images.

    duane

On May 23, 2006, at 3:16 PM, Thoralf Seewald wrote:

> Dear ImageJ users,
> I am trying to increase the memory for imageJ. I need around 3.8 GB  
> for processing plug-ins I want to go through. But after the change  
> in the command line greater than 2600mb the software does not start  
> anymore with the notice, that there is not enough Virtual Memory.
>
> I am usin a 2x3.2 GHz Intel Xeon with Fedora Core 5 (32bit).
>
> I would great appreciate an idea or help with my little problem.
>
> Thank you in advance,
>
>
> Thoralf Seewald.
>
> --
> Hightech Research Center Basel (HFZ)
> _______________________________
>
> Mail:  [hidden email]
>        [hidden email]
> Fon:   +49 /  30 - 206.87.602
> Mobil: +49 / 176 - 222.02.507
>        +41 /  76 - 50.55.798
> _______________________________
Reply | Threaded
Open this post in threaded view
|

Re: not enough VM

Thoralf Seewald
Hi Duane,
yes, I need this 3.8GB, because I have different stacks of images (around 8.7MB each image), which are around 3.0-3.1GB big each. And I can't divide this stack into two. I need all images in the memory at the same time. The rest of 700MB is needed to get my plugin started.
Maybe I have to go to the kernel of fedora to change some variables. But I have never done it before. Do you have any idea?
Do you know something about it? How can I solve this problem?

THX,
Thoralf.




You got 2600MB?  Consider yourself lucky.  With a 32 bit JVM (which  
is what most of us have) you max out around 1500MB.

The bigger question, though, is why do you need 3.8GB?  That equates  
to a VERY large image, or a large stack of large images.

    duane

--

_______________________________

Mail:  [hidden email]
       [hidden email]
Fon:   +49 /  30 - 206.87.602
Mobil: +49 / 176 - 222.02.507
       +41 /  76 - 50.55.798
_______________________________
Reply | Threaded
Open this post in threaded view
|

Re: not enough VM

Gabriel Landini
On Wednesday 24 May 2006 16:53, Thoralf Seewald wrote:
> yes, I need this 3.8GB, because I have different stacks of images (around
> 8.7MB each image), which are around 3.0-3.1GB big each. And I can't divide
> this stack into two. I need all images in the memory at the same time. The
> rest of 700MB is needed to get my plugin started. Maybe I have to go to the
> kernel of fedora to change some variables. But I have never done it before.
> Do you have any idea? Do you know something about it? How can I solve this
> problem?

I do not think that you can allocate that amount of memory to java in the 32
bit version. (Read the archive, this has been discussed before).

You could open the stack as a virtual stack (again look in the IJ site for the
plugin).

G.
Reply | Threaded
Open this post in threaded view
|

Re: not enough VM

Huw Blackwell
In reply to this post by Thoralf Seewald
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Duane,

You're running into a hardware problem. Using a 32bit computer (as you
are) you are physically limited to 4GB of RAM+virtual memory, unless you
start doing some VERY fancy tricks which probably won't help your JVM.
As a result the limits on the 32 bit java virtual machine are set lower,
to give you some RAM for the rest of your system to play with. Loading
3.8 GB of images will probably be very difficult, if not impossible
simply because of this limitation. One way to solve your problems is run
your program on a 64bit machine, (I.e an Opteron, Atlon 64 or an intel
processor with EM64T) using the 64bit Java virtual machine, and your
problem should go away.

Chewwit


Thoralf Seewald wrote:

> Hi Duane,
> yes, I need this 3.8GB, because I have different stacks of images (around 8.7MB each image), which are around 3.0-3.1GB big each. And I can't divide this stack into two. I need all images in the memory at the same time. The rest of 700MB is needed to get my plugin started.
> Maybe I have to go to the kernel of fedora to change some variables. But I have never done it before. Do you have any idea?
> Do you know something about it? How can I solve this problem?
>
> THX,
> Thoralf.
>
>
>
>
> You got 2600MB?  Consider yourself lucky.  With a 32 bit JVM (which  
> is what most of us have) you max out around 1500MB.
>
> The bigger question, though, is why do you need 3.8GB?  That equates  
> to a VERY large image, or a large stack of large images.
>
>     duane
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEdJZW6iLyNw8zCE4RAmVNAJ9d/5vp/2Oif2ndGKDpo3fAHMPiIgCgkL0S
iEHIgO+hwBNl31yGdNGeHdQ=
=14sf
-----END PGP SIGNATURE-----
Reply | Threaded
Open this post in threaded view
|

Re: not enough VM

Thoralf Seewald
In reply to this post by Gabriel Landini
Hi Gabriel Landini, Hi Huw Blackwell,
Thank you for responding. I will have a look into the archive and look forward to use a 64bit machine in any way.

Best regards,

Thoralf.