Greetings! Gunter Königsmann <gun...@peterpall.de> writes:
>> >> gcl's decision to consume all available memory before GCing seems very >> unfriendly, and would seem to make the GC pause huge. >> By default GCL will start gc at 1/2 physical memory, then progressively increase aggressivity to maximum at 3/4. The parameters are all adjustable with environment variable settings. > > What I like about gcl is that if you start several maxima instances at > the same time they seem to be able to communicate about which instance > uses how much memory. > Glad to see this feature is getting some exercise, as I think it needs to be turned on by default at release. There is a small overhead which I regret, but communicating to multi-instance users how to setup their environment seems to forbidding an alternative. Thanks for all your work on maxima! Take care, > I've now committed the 2nd patch. > > The 1st try to do so resulted in a "bad gateway" error. The 2nd one > worked with public key auth again => seems like sf.net is currently > working on the git stack. > > Kind regards, > > Gunter. > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Maxima-discuss mailing list > maxima-disc...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/maxima-discuss > > > -- Camm Maguire c...@maguirefamily.org ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah _______________________________________________ Gcl-devel mailing list Gcl-devel@gnu.org https://lists.gnu.org/mailman/listinfo/gcl-devel