From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: /srv/bzr/emacs/emacs-24 r111116: eval-after-load fix Date: Fri, 04 Jan 2013 19:58:43 +0900 Message-ID: <87sj6hb4f0.fsf@uwakimon.sk.tsukuba.ac.jp> References: <878v8b839k.fsf@yandex.ru> <871ue3c5ek.fsf@uwakimon.sk.tsukuba.ac.jp> <50E669D2.6030808@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1357297140 29457 80.91.229.3 (4 Jan 2013 10:59:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 4 Jan 2013 10:59:00 +0000 (UTC) Cc: emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 04 11:59:16 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Tr4zY-0000oU-Ql for ged-emacs-devel@m.gmane.org; Fri, 04 Jan 2013 11:59:12 +0100 Original-Received: from localhost ([::1]:47373 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tr4zJ-0006gs-Mz for ged-emacs-devel@m.gmane.org; Fri, 04 Jan 2013 05:58:57 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:35392) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tr4zH-0006gm-0G for emacs-devel@gnu.org; Fri, 04 Jan 2013 05:58:56 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tr4zE-0005w6-IU for emacs-devel@gnu.org; Fri, 04 Jan 2013 05:58:54 -0500 Original-Received: from mgmt2.sk.tsukuba.ac.jp ([130.158.97.224]:38656) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tr4zE-0005tQ-9c for emacs-devel@gnu.org; Fri, 04 Jan 2013 05:58:52 -0500 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt2.sk.tsukuba.ac.jp (Postfix) with ESMTP id 312F29708C6; Fri, 4 Jan 2013 19:58:44 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id EAB441A3222; Fri, 4 Jan 2013 19:58:43 +0900 (JST) In-Reply-To: <50E669D2.6030808@yandex.ru> X-Mailer: VM undefined under 21.5 (beta32) "habanero" b0d40183ac79 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 130.158.97.224 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:156078 Archived-At: Dmitry Gutov writes: > On 03.01.2013 7:27, Stephen J. Turnbull wrote: > > Glenn Morris writes: > > > > > Maybe. (Personally, I doubt any of these purecopy calls have any > > > non-negligible effect.) > > > > FWIW, XEmacs did away with purespace ages ago with no complaints from > > anybody. (We still have `purecopy' for API compatibility with Emacs, > > but it's a no-op now.) > > > > That's damning with faint praise, of course, but it's a data point. > > Is it really faint, though? Yes, it is faint. I have no numbers on comparative performance in speed or size, and I wouldn't be surprised if it increases total memory usage for some multi-xemacs-process cases (see Andreas's post). The arguments that killed purespace for us were (1) most users (including most of those who argued for keeping purespace :-) are in one-xemacs-process-per-machine workflows, and (2) in theory modern virtual memory management by OSes (we were specifically influenced by Linux and Windows) should produce most of the benefits of purespace anyway, since the dumped code contains only a few writable objects, and those tend to be clumped on a very few pages per file, such that the potentially written pages might be measured in 100s of KB out of the 3-5 MB (at that time) of XEmacs memory. I'm not sure I believe (2), though. Steve