From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: On elisp running native Date: Fri, 29 Nov 2019 16:43:21 +0000 Message-ID: References: <83zhgeoh0k.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="13016"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (berkeley-unix) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 29 17:43:37 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iajMl-0003Gc-VP for ged-emacs-devel@m.gmane.org; Fri, 29 Nov 2019 17:43:36 +0100 Original-Received: from localhost ([::1]:60846 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iajMk-0000qE-S0 for ged-emacs-devel@m.gmane.org; Fri, 29 Nov 2019 11:43:34 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36893) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iajMc-0000fu-I9 for emacs-devel@gnu.org; Fri, 29 Nov 2019 11:43:27 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iajMa-00059Z-BE for emacs-devel@gnu.org; Fri, 29 Nov 2019 11:43:25 -0500 Original-Received: from mx.sdf.org ([205.166.94.20]:64119) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iajMY-00054b-In; Fri, 29 Nov 2019 11:43:22 -0500 Original-Received: from sdf.org (IDENT:akrl@sverige.freeshell.org [205.166.94.5]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id xATGhLlj016282 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Fri, 29 Nov 2019 16:43:21 GMT Original-Received: (from akrl@localhost) by sdf.org (8.15.2/8.12.8/Submit) id xATGhLSn021257; Fri, 29 Nov 2019 16:43:21 GMT In-Reply-To: <83zhgeoh0k.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 29 Nov 2019 17:10:19 +0200") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 205.166.94.20 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:242883 Archived-At: Eli Zaretskii writes: >> From: Andrea Corallo >> Date: Fri, 29 Nov 2019 14:59:16 +0000 >> Cc: emacs-devel@gnu.org >> >> | | byte-compiled | native-compiled | speed-up | >> |-------------+---------------+-----------------+----------| >> | interactive | 27s | 19s | 1.4x | >> | batch | 15s | 8s | 1.9x | >> >> To me makes quite sense that in interactive there's less difference >> cause of the re-display done in C anyway. > > Regardless of the speed-up due to using native code, it sounds strange > to me that byte-compiling interactively takes twice the time it takes > non-interactively. I have hard time convincing myself that redisplay > has such a profound effect on byte compilation, since byte-compiling a > file normally yields one or two lines of output, regardless of the > size of the file being compiled. > > Does the timing change if you delete the window showing the > compilation log? In that case, redisplay is not involved at all. > > Also, was the interactive session started only once, and then used for > compiling all the files? Or was it restarted anew for each > compilation? If the latter, then the slow-down is probably due to a > slower startup of a GUI session. > > Thanks. > Hi Eli, yeah sounds strange. I'm very possibly doing something wrong here. What I'm doing is starting a fresh "emacs -Q" and then measuring the time of: (mapc #'byte-compile-file (directory-files "~/emacs/lisp" t "el$")) Then is one single start of the GUI for all compilations. I see an intense message activity going on in the mini-buffer so maybe that's the reason? Question how could I delete the compilation log without interrupting the compilation it-self? Bests Andrea -- akrl@sdf.org