The kernel is configured to be 4GB (CONFIG_HIGHMEM4G) physical ram
and it looks like we have about 3.7GB of memory available.
Any else look incorrect?
$ cat /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 3776847872 78446592 3698401280 0 9785344 28241920
Swap: 1052794880 0 1052794880
MemTotal: 3688328 kB
MemFree: 3611720 kB
MemShared: 0 kB
Buffers: 9556 kB
Cached: 27580 kB
SwapCached: 0 kB
Active: 25472 kB
Inactive: 15720 kB
HighTotal: 2817472 kB
HighFree: 2784680 kB
LowTotal: 870856 kB
LowFree: 827040 kB
SwapTotal: 1028120 kB
SwapFree: 1028120 kB
Tom Badran wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wednesday 09 Oct 2002 10:59 pm, Kristian G. Kvilekval wrote:
> > We have several bio-computing experiments that need over
> > 2GB of heap. We are running on linux-2.4.19 on machines
> > with 4GB of memory.
> >
> > $ java -version
> > java version "1.3.1"
> > Java(TM) 2 Runtime Environment, Standard Edition (build
> > Blackdown-1.3.1-FCS)
> > Java HotSpot(TM) Client VM (build Blackdown-1.3.1-FCS, mixed mode)
> >
> > Allocating 1.9GB appears to work (will crash sometime though).
> >
> > $ java -Xmx1900m J
> >
> > Allocating 2GB and above always fails.
> >
> > $java -Xmx2000m J
> > Error occurred during initialization of VM
> > Could not reserve enough space for object heap
> >
> > Can anybody suggest a solution or work around.
>
> It looks like you dont have himem properly configured in your kernel. You
> should be able to get a heap of 4GB - the java vm internal memory etc so i
> would say at least 3.7GB on a bad day. I would check how you have your kernel
> configured. The kernel may also not be seeing all of your memory, this is
> easily fixed by passing the mem=** option to the kernel, this is documented
> in the linux kernel source (normally /usr/src/linux/Documentation).
>
> This should point you in the right direction
>
> Tom
>
--
Kristian G. Kvilekval
email:[EMAIL PROTECTED] office:(805)893-4178 http://www.cs.ucsb.edu/~kris
