From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Time to merge scratch/correct-warning-pos into master, perhaps? Date: Tue, 25 Jan 2022 17:21:25 -0500 Message-ID: References: <837darmygd.fsf@gnu.org> <58bb8030d59733b52b8d@heytings.org> <83r18zkmd5.fsf@gnu.org> <835yq9ls7j.fsf@gnu.org> <058b682b11240176288f@heytings.org> <83h79tjd2f.fsf@gnu.org> <058b682b11f58780b580@heytings.org> <83v8y8ij39.fsf@gnu.org> <6a5bb5a08b3d764611f9@heytings.org> <6a5bb5a08b6337d733c5@heytings.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30126"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Alan Mackenzie , mattiase@acm.org, Eli Zaretskii , larsi@gnus.org, emacs-devel@gnu.org To: Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jan 25 23:23:40 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 1nCUDz-0007fp-8t for ged-emacs-devel@m.gmane-mx.org; Tue, 25 Jan 2022 23:23:39 +0100 Original-Received: from localhost ([::1]:33054 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nCUDx-0000ex-9x for ged-emacs-devel@m.gmane-mx.org; Tue, 25 Jan 2022 17:23:37 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:48884) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nCUBw-0008NO-P0 for emacs-devel@gnu.org; Tue, 25 Jan 2022 17:21:33 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:1184) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nCUBu-0006AL-M7; Tue, 25 Jan 2022 17:21:32 -0500 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id D7BDC4428D6; Tue, 25 Jan 2022 17:21:27 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 9DEB34428C7; Tue, 25 Jan 2022 17:21:26 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1643149286; bh=q+Tw84ZR/y/Wcg2NeCxhyVu2gaTK5ezG9p0M9qPsX0c=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=MNyBIwUnM3PVLUmmoDCqBAy8S+miznde0i8L/Wtim3Aa49Ruvsqqtzy5AjyUlxjYR xOlcileU3F7RIyCoh8ou1g+hITsaOWoJycfWjEso592u6NC7wDEAPkCUMEHyF4MHSd 5AT1MEDNSo/nQxyLATaN6Vs5WOi5WqQxGtjdYGB7ZtBJEkS8etE2GcVuIdmPKKo1w4 L+kglVEvSgR9MMfnu/48IlJcC/3EjRkeefHabNRf4hZ6b0mabOvq++jKjG7sIsSmXK qJ//VTxX2Yg4EV4+ze3T5b4CsSQw7wmL6RCoozkHkesnEBeg+EP3cyM+/J1xNBt78S EELOsD/PezrTg== Original-Received: from pastel (unknown [216.154.30.173]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 531B9120807; Tue, 25 Jan 2022 17:21:26 -0500 (EST) In-Reply-To: <6a5bb5a08b6337d733c5@heytings.org> (Gregory Heytings's message of "Tue, 25 Jan 2022 21:38:24 +0000") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:285402 Archived-At: Gregory Heytings [2022-01-25 21:38:24] wrote: >> More importantly, I wonder how slowing down EQ by a factor of 2 can end up >> costing 10% of runtime when running the test suite. I think this >> deserves investigation. > Do you have an idea how this could be investigated? Usually such slowdown don't come from everywhere at the same time. So you need to "slice" our total time into subelements, and presumably some of those elements show a higher slowdown, so you can focus on those and start slicing them further. As you get closer to the source, the slowdown should become more marked. Stefan