GNU bug report logs - #75672
31.0.50; scratch/igc memory usage/collection issues

Previous Next

Full log

Message #53 received at 75672 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Pip Cet <pipcet <at> protonmail.com>
Cc: alexispurslane <at> pm.me, 75672 <at> debbugs.gnu.org
Subject: Re: bug#75672: 31.0.50; scratch/igc memory usage/collection issues
Date: Mon, 20 Jan 2025 18:52:26 +0200

> Date: Mon, 20 Jan 2025 14:19:29 +0000
> From: Pip Cet <pipcet <at> protonmail.com>
> Cc: Alexis Purslane <alexispurslane <at> pm.me>, 75672 <at> debbugs.gnu.org
> 
> "Eli Zaretskii" <eliz <at> gnu.org> writes:
> 
> >> Cc: 75672 <at> debbugs.gnu.org
> >> Date: Mon, 20 Jan 2025 02:33:15 +0000
> >> From:  Alexis Purslane via "Bug reports for GNU Emacs,
> >>  the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
> >>
> >> committed                                    1       400138240  400138240             0
> >> pause-time                                 nil             0.1        nil           nil
> >> reserved                                     1       536875008  536875008             0
> >> spare                                      nil            0.75        nil           nil
> >> spare-committed                              1       217436160  217436160             0
> >
> > AFAIU, these 3 values mean that MPS uses about 1.15GB of memory
> > (unless "reserved" includes "committed").  If "reserved" means memory
> 
> MPS "reserved" means "mmapped, not necessarily faulted in or used".
> MPS "committed" means "faulted in and possibly in use by MPS or the
> client program".
> MPS "spare-committed" means "in use by MPS, not the client program".
> 
> So committed - spare-commited is how much usable memory MPS thinks has
> been allocated, about 183 MB.

I agree, but did I say something different?

The question now becomes: how was the 1.5GB figure Alex reported
measured? did it include the reserved memory, or didn't it?

> It's virtual memory: MPS assumes virtual memory is very cheap.  That's
> not really true for processes that fork() a lot, so this assumption may
> have to be fine-tuned.

AFAIK, fork'ed process uses copy-on-write, so we should be okay.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.