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: Time to merge scratch/correct-warning-pos into master, perhaps? Date: Mon, 24 Jan 2022 05:37:20 +0200 Message-ID: <835yq9ls7j.fsf@gnu.org> References: <83mtjwzwkb.fsf@gnu.org> <87r198ytog.fsf@gnus.org> <87zgnvyb5y.fsf@gnus.org> <87bl03j10s.fsf@gnus.org> <9D116A4B-622F-4C80-83E6-2CDD7ED9AD25@acm.org> <58bb8030d532070ed420@heytings.org> <838rv7mzn4.fsf@gnu.org> <58bb8030d5ec3a6bde9f@heytings.org> <837darmygd.fsf@gnu.org> <58bb8030d59733b52b8d@heytings.org> <83r18zkmd5.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40241"; mail-complaints-to="usenet@ciao.gmane.io" Cc: mattiase@acm.org, larsi@gnus.org, emacs-devel@gnu.org, monnier@iro.umontreal.ca, acm@muc.de To: Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 24 04:39:04 2022 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 1nBqC8-000AHV-7a for ged-emacs-devel@m.gmane-mx.org; Mon, 24 Jan 2022 04:39:04 +0100 Original-Received: from localhost ([::1]:36820 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nBqC6-0004OK-VA for ged-emacs-devel@m.gmane-mx.org; Sun, 23 Jan 2022 22:39:02 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:34518) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nBqAi-00031u-QI for emacs-devel@gnu.org; Sun, 23 Jan 2022 22:37:36 -0500 Original-Received: from [2001:470:142:3::e] (port=57464 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nBqAh-0005L2-7e; Sun, 23 Jan 2022 22:37:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=EyGfEbv0VBleFSTI4WTrYwFbgdQXmpgZMl4GUvTkT6s=; b=LFFHpgrtf2+w HO7/KfTZahMbMZCj3+KE8Uegl2FpWCohekpOFtNgivbPhh+4JCuFYRiirmRvR69eddbYLbBwzvxB7 jEcgONGl7VLr2NyZ6SNXqqm/HKt3MowmOQ5nAmZqbK0HKE3EQiSa5LqCxlIx6Scf2s6E9tGsqqCzC iA8xPoBbKt6h+HQ1zsu1DXahOtu2gH9P/wAprWf2Yml4RZuEsJgXGOvVxtkR0zwij4dQkZ0kPAs3B XChzo/LDbTYKPliAxwcqVe57ihRTSDdyKAIXRNbBs5bOs2ClI+TVmc4YFaa3PF1vpXyiwx2CYMw4D EYe8quyG0DjY7zRd9SKX/g==; Original-Received: from [87.69.77.57] (port=3747 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nBqAg-0006FC-Ln; Sun, 23 Jan 2022 22:37:34 -0500 In-Reply-To: (message from Gregory Heytings on Sun, 23 Jan 2022 21:53:24 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:285282 Archived-At: > Date: Sun, 23 Jan 2022 21:53:24 +0000 > From: Gregory Heytings > cc: mattiase@acm.org, larsi@gnus.org, acm@muc.de, monnier@iro.umontreal.ca, > emacs-devel@gnu.org > > >> In short, the compilation time in make check is slower (which is > >> expected), but the execution time in make check is also consistently > >> ~7% slower. > > > > How did you separate compilation times from execution times, > > > > See the attached patch. > > > > > and what does "execution time" stand for -- is that elapsed time, CPU > > time, something else? > > > > The first time printed by "time", that is, the wall clock time. If you are measuring wallclock time, I don't see how the overall slowdown is a reliable measure of any code performance. The test suite includes quite a few tests that deliberately wait for some seconds for various reasons, and those times aren't affected by the byte code or the interpreter. We need to measure CPU time.