Re: [Maxima-discuss] gcl memory usage

[Gunter K. <gu...@pe...>]

On 24.04.2018 18:34, Gunter Königsmann wrote:
> 
> 
> Am 24. April 2018 17:52:09 MESZ schrieb Raymond Toy <toy...@gm...>:
>>>>>>> "Gunter" == Gunter Königsmann <gu...@pe...> writes:
>>
>>    Gunter> Potential solution since with
>> Gunter> https://gitlab.gnome.org/GNOME/gnome-shell/issues/64 a maybe
>> similar
>>    Gunter> issue has hit the press:
>>
>> Gunter> Would it be reasonable to manually trigger the garbage
>> collector
>>    Gunter> - after executing a maxima command in cl-user::run () and
>>    Gunter> - after running a testbench file
>>    Gunter> - after each read_nested_list() and read_matrix() ?
>>
>> Does any othe lisp require such GC hacks?  I'm ok with providing hints
>> to the underlying GC about how maxima uses memory (how many
>> generations there are, how often to collect each generation, how big
>> each generation can be before GC and so on), but I'm not really
>> fond of manually calling GC at random places.  It's just so, umm,
>> random.
>>

Seems like the gc hack (I've commited it as branch
GclHintGarbageCollector) doesn't help with gcl:

With the hack gcl manages to finish the test bench. But it does so only
if the system is running in single-user mode and no big application
(thunderbird, firefox) is running.

Kind regards,

   Gunter.