From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Memory usage report Date: Fri, 18 Sep 2020 09:25:40 +0300 Message-ID: <83imcb61p7.fsf@gnu.org> References: <87lfh8kyot.fsf@gnus.org> <83k0ws5hzt.fsf@gnu.org> <87h7rwkxtk.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30622"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 18 08:27:11 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kJ9rS-0007pf-Rz for ged-emacs-devel@m.gmane-mx.org; Fri, 18 Sep 2020 08:27:10 +0200 Original-Received: from localhost ([::1]:47048 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kJ9rR-0001en-Uv for ged-emacs-devel@m.gmane-mx.org; Fri, 18 Sep 2020 02:27:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49424) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kJ9q0-0000lE-Eg for emacs-devel@gnu.org; Fri, 18 Sep 2020 02:25:40 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:56878) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kJ9pu-00042C-Lr; Fri, 18 Sep 2020 02:25:36 -0400 Original-Received: from [176.228.60.248] (port=1512 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kJ9po-0005An-BJ; Fri, 18 Sep 2020 02:25:29 -0400 In-Reply-To: <87h7rwkxtk.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 17 Sep 2020 21:28:07 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:256051 Archived-At: > From: Lars Ingebrigtsen > Cc: emacs-devel@gnu.org > Date: Thu, 17 Sep 2020 21:28:07 +0200 > > >> (garbage-collect) > > > > This doesn't include memory we allocate for stuff that isn't Lisp > > objects. > > Indeed. A useful memory usage report would need more data, but it's a > starting point... Not that I'd object to formatting this in better ways (especially since a package to do that is already on ELPA), but from experience, memory related problems are very rarely in GC-related areas. So for diagnosing memory leaks, the GC report is not very useful. See, for example, the currently on-going discussion on the bug list, where someone with a 5GB RSS of the Emacs process posted the output of garbage-collect, which shows fewer objects and less memory taken by them than in my 13-day old Emacs session whose total VM size is just 0.5GB.