Re: [Maxima-discuss] [Maxima-commits] [git] Maxima CAS branch master updated. branch-5_47-base-1896-g4c8127730

[Camm M. <ca...@ma...>]

Greetings!  There is (hopefully) some useful commentary on this in the
release notes.

Most briefly

export GCL_MEM_BOUND=29

will run in no more than 1Gb of memory, which is sufficient to build GCL
and most other things.

In more detail, the environment variables relevant to memory management
and their defaults are described in the info pages:

GCL_MEM_MULTIPLE
GCL_MEM_BOUND
GCL_MULTIPROCESS_MEMORY_POOL
GCL_GC_ALLOC_MIN
GCL_GC_PAGE_MIN
GCL_GC_PAGE_MAX

The basic idea of the defaults is to start gc at about half of available
physical memory, and place a hard limit at physical memory + swap.  This
may need revisiting in cases where swap is large relative to physical.

Take care,


Raymond Toy <toy...@gm...> writes:

> On 4/23/25 10:12 AM, Camm Maguire wrote:
>
>  Greetings!
>
> What’s the magic to limit gcl from using too memory? While building maxima and doing some other stuff, my laptop (16 GB) froze and I had to power cycle it
> losing whatever I was working on. 
>
> My desktop with 32 GB killed my gcl build for using too much memory. (I was probably running 2 VMs at the time, though, but still.)
>
> Whatever the defaults are for gcl, it’s very, very unfriendly. I would think gcl should be able to build itself and maxima using no more than 4 GB of memory.
> Cmucl can build itself and maxima with just 512 MB heap and certainly less than 1 GB. I don’t recall having this issue with gcl 2.6.14.
>
> &#8203;
>

-- 
Camm Maguire			     		    ca...@ma...
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah