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: Tue, 25 Jan 2022 14:26:11 +0200 Message-ID: <83pmoghuho.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> <835yq9ls7j.fsf@gnu.org> <058b682b11240176288f@heytings.org> <83h79tjd2f.fsf@gnu.org> <058b682b11f58780b580@heytings.org> <83v8y8ij39.fsf@gnu.org> <6a5bb5a08b3d764611f9@heytings.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12666"; mail-complaints-to="usenet@ciao.gmane.io" Cc: mattiase@acm.org, larsi@gnus.org, acm@muc.de, monnier@iro.umontreal.ca, 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 13:37:39 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 1nCL4s-00034f-Du for ged-emacs-devel@m.gmane-mx.org; Tue, 25 Jan 2022 13:37:38 +0100 Original-Received: from localhost ([::1]:49580 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nCL4r-00074F-5U for ged-emacs-devel@m.gmane-mx.org; Tue, 25 Jan 2022 07:37:37 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58700) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nCKu2-0002ol-2T for emacs-devel@gnu.org; Tue, 25 Jan 2022 07:26:26 -0500 Original-Received: from [2001:470:142:3::e] (port=32976 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 1nCKu0-0004bU-HW; Tue, 25 Jan 2022 07:26:25 -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=0S4+/ZSrVvTUioldN81OfbyOKzLwRPpgAXwkUeHdHbg=; b=XDfdhXPvLiBA I4EU9C7RSb2Mxt73dABOiniT3iwwHKWdCsnTemQ2Oa/ZDLq6VqpoTlGi1tGlFBBZMWZuTFQh4Yzvh 5KI4CCM8Q5Q3iA7Mh0Uh0S0tglIKjrtAojsqPqreYbv+DNiIsX4JcceeLxz05PZNC14zmDGk2MJK5 XTiGgAR1UqTXF6eAgxkIS9bMMVXON+0lo49ruNeogMXWrYarPOeNQ6fuB55r7KFIKYhXcSGSTPFnZ wJe8bRolISUA1mY98OOxmcnrP9Bl/0Why9w1XF8DImDz32Bvj6KEp+pITcO5Vh8ZNNANlMCCWDEAV nj3BSAYOoYjutOTITE9VQA==; Original-Received: from [87.69.77.57] (port=4900 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 1nCKtz-00052r-AI; Tue, 25 Jan 2022 07:26:24 -0500 In-Reply-To: <6a5bb5a08b3d764611f9@heytings.org> (message from Gregory Heytings on Tue, 25 Jan 2022 08:59:00 +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:285364 Archived-At: > Date: Tue, 25 Jan 2022 08:59:00 +0000 > From: Gregory Heytings > cc: mattiase@acm.org, larsi@gnus.org, emacs-devel@gnu.org, > monnier@iro.umontreal.ca, acm@muc.de > > I think you understood what I meant: bytecode execution in Emacs is now, > on average, about 10% slower. Are there other benchmarks (not > micro-benchmarks) that could be used to reach what you would consider a > mature conclusion? I think we need more measurements in scenarios closer to actual Emacs usage. One is intensive display operation -- I think Alan posted something to that effect. Another could be starting Gnus to read a large newsgroup. Yet another could be reindent a large piece of C or Python or Lisp code. Perhaps also "M-x occur" through a large buffer. Stuff like that -- any command that tends to be used frequently and is known to take a tangible amount of time.