From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: michael schuldt Newsgroups: gmane.emacs.devel Subject: Re: Should we land Lisp reader optimizations? Date: Wed, 21 Jun 2017 19:56:06 -0700 Message-ID: References: <83y3snx6b7.fsf@gnu.org> <56EA228B-387F-4983-A91E-97ACFE56F42F@raeburn.org> <83a852wuk0.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c061cd84b4d7b055283a088" X-Trace: blaine.gmane.org 1498100217 25804 195.159.176.226 (22 Jun 2017 02:56:57 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 22 Jun 2017 02:56:57 +0000 (UTC) Cc: Eli Zaretskii , Ken Raeburn , emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 22 04:56:53 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dNsIf-0006PY-Jl for ged-emacs-devel@m.gmane.org; Thu, 22 Jun 2017 04:56:53 +0200 Original-Received: from localhost ([::1]:56774 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dNsIi-0003i3-Vm for ged-emacs-devel@m.gmane.org; Wed, 21 Jun 2017 22:56:57 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50539) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dNsI1-0003Vz-4Y for emacs-devel@gnu.org; Wed, 21 Jun 2017 22:56:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dNsI0-0008Pj-58 for emacs-devel@gnu.org; Wed, 21 Jun 2017 22:56:13 -0400 Original-Received: from mail-qk0-x22b.google.com ([2607:f8b0:400d:c09::22b]:35356) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dNsHx-0008NW-DI; Wed, 21 Jun 2017 22:56:09 -0400 Original-Received: by mail-qk0-x22b.google.com with SMTP id 16so2630119qkg.2; Wed, 21 Jun 2017 19:56:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=m1DvXHkvf+9R/91uJTX4cYFolt9LDX52x/MCHnnZHf4=; b=JFqfx/BZVXn7GjCUakxx25fU8DIapfTgOSGcacQwJMUrODyFFRq+kOOCpHp0ueTLV4 9RxCLJZL6vwvBzKB/ILJzmzQ1YQYF4ksWNlRXTpMjHQNeE40cPNlKH1SbjJaH13jzWDn On6bTc7HVDUT3uixN7hexVHHlmSASO8VrDTtrT+yXr4GwsQxNmGAsUjeE8KPu2O14RhE ODMeZRnhzxWYAbEkz0ihBHukNUNRODl+aG26W/OTPcwswnBA2DzAamiVrq8zCEPGrV+a wtQcAXQlrcua3c8IlGeY9p+bj9/hYbBtOcXyNQRkisDXR+K0vkPaidz5rG/GTjpToVa3 7dKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=m1DvXHkvf+9R/91uJTX4cYFolt9LDX52x/MCHnnZHf4=; b=dzbdOzRnr1rHwz41+TC9iLgi0KtIRrowLSIMj9xWMWfjYb1fAhdkCozpdx7EVTvWDb ybNr4nHp89wlF6wQa012yosaPQdSvQuhQr5X426UfGNUIyFHgZzU4ReTPjGVbUfg4TCK gEyL4NbkSuEZR4zDrFWmlKVsD+TUe4e4iDyVpB2ivYYz64JRA3smtxPx+o6BHOcn599B GMCFgMXAHxkvPerbE+ib5c6Jxn1sWjIq+goJ75L0htDprPq7+LPKX1Qtt2iwRK5yMQrM e6lOsnfeZgQUyE1sSbUahb/VCXnmJGgCw6/aJ1SVAigxHd2HaRKYAcsju70ZOT7Iv8Gt qcCA== X-Gm-Message-State: AKS2vOzyorlefRuCIp4MM5WjcGTsk4xXgHiNhbSEfckOMOYxZR+q0qeu L3xHuor0sENNgovimz7Vv6v5JP1dzaJ5s+A= X-Received: by 10.55.158.137 with SMTP id h131mr346354qke.246.1498100167034; Wed, 21 Jun 2017 19:56:07 -0700 (PDT) Original-Received: by 10.140.108.197 with HTTP; Wed, 21 Jun 2017 19:56:06 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:400d:c09::22b X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:215875 Archived-At: --94eb2c061cd84b4d7b055283a088 Content-Type: text/plain; charset="UTF-8" I was actually only thinking about disabling it while reading the big .elc file, not all the time. But in either case Ken seems to make it clear that it does not really matter - GC overhead is small when reading normal files and already minimized for the big .elc read On Wed, Jun 21, 2017 at 6:58 PM, Richard Stallman wrote: > > Since the time spent in GC appears so significant, why not disable GC > while > > reading? > > That could bloat the total memory size of Emacs, with garbage scattered > among > the actually used memory so that no entire blocks could be freed. > Is this scattered memory ever compacted? I've had times where Emacs refuses to let go of massive amounts of seemingly unused memory, despite forced GCs. Maybe this was the problem --94eb2c061cd84b4d7b055283a088 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I was actually only thinkin= g about disabling it while reading the big .elc file, not all the time.
But in either case Ken seems to make it clear that it does not really = matter -
GC overhead is small when reading normal files and already mini= mized for the big .elc read

On Wed, Jun 21, 2= 017 at 6:58 PM, Richard Stallman <rms@gnu.org> wrote:
=C2=A0 > Since the time spent in GC appears so significant, why not disa= ble GC while
=C2=A0 > reading?

That could bloat the total memory size of Emacs, with garbage scatte= red among
the actually used memory so that no entire blocks could be freed.
<= div>
Is this scattered memory ever compacted?
I've had= times where Emacs refuses to let go of massive amounts of seemingly unused=
memory, despite forced GCs. Maybe this was the problem
<= br>
--94eb2c061cd84b4d7b055283a088--