GNU bug report logs -
#45200
Wishlist: There should be a `malloc-trim' function
Previous Next
Reported by: Konstantin Kharlamov <hi-angel <at> yandex.ru>
Date: Sat, 12 Dec 2020 18:44:02 UTC
Severity: wishlist
Fixed in version 29.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #101 received at 45200 <at> debbugs.gnu.org (full text, mbox):
On February 3, 2021 8:04:21 AM GMT+02:00, Konstantin Kharlamov <hi-angel <at> yandex.ru> wrote:
> On Tue, 2021-02-02 at 23:50 -0500, Stefan Monnier wrote:
> > > > with malloc_trim:
> > > > (8.920371394 232 2.106283245)
> > > > (9.038083601 231 2.060810826)
> > > > (9.140798641 231 2.0594013240000004)
> > > >
> > > > without malloc_trim:
> > > > (8.987097209 232 2.070143482)
> > > > (8.700478084 231 1.7745506179999997)
> > > > (8.781121056 231 1.7870093610000004)
> > > >
> > > > The difference is just 3-4% (8.7 / 9 ≈ 0.9666666667). It looks
> to me
> > > > insignificant enough to not show up anywhere during interactive
> work
> > > > with Emacs.
> > >
> > > It's indeed not too costly, but what about the upside?
> >
> > BTW, maybe a better way forward than trying to convince us that it's
> > a good default (which could be hard if the upside is a reduction of
> the
> > memory use by a few percent: for many people it might be less
> > relevant/noticeable than the corresponding few percents lost in
> speed)
> > is to provide a patch that adds a new *ELisp* function that calls
> > `malloc_trim`, which you can then add to `post-gc-hook` in your init
> > file when your usage pattern makes it useful.
>
> Upside indeed is the memory reduction.
How much memory reduction? Can you show the numbers?
This bug report was last modified 3 years and 78 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.