From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#58558: 29.0.50; re-search-forward is slow in some buffers Date: Tue, 18 Oct 2022 20:19:24 +0200 Message-ID: <87wn8x9eqb.fsf@gnus.org> References: <877d10r21x.fsf@localhost> <87zgdwyvkt.fsf@gnus.org> <87ilkk6ri5.fsf@localhost> <87v8okjei9.fsf@gnus.org> <87tu44jdce.fsf@localhost> <87czasjd9j.fsf@gnus.org> <87k050nio5.fsf@localhost> <87zgdwhw0z.fsf@gnus.org> <83sfjo3tfw.fsf@gnu.org> <878rlfjmjh.fsf@localhost> <87mt9tbbbp.fsf@gnus.org> <8335bl18lo.fsf@gnu.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="7249"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 58558@debbugs.gnu.org, yantar92@posteo.net, monnier@iro.umontreal.ca To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Oct 18 20:23:20 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1okrFI-0001fx-US for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 18 Oct 2022 20:23:20 +0200 Original-Received: from localhost ([::1]:46116 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1okrFH-0002ZP-Gl for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 18 Oct 2022 14:23:19 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44306) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1okrC6-0000ss-3S for bug-gnu-emacs@gnu.org; Tue, 18 Oct 2022 14:20:06 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:55015) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1okrC5-00029P-QM for bug-gnu-emacs@gnu.org; Tue, 18 Oct 2022 14:20:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1okrC5-0000F5-Ln for bug-gnu-emacs@gnu.org; Tue, 18 Oct 2022 14:20:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 18 Oct 2022 18:20:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 58558 X-GNU-PR-Package: emacs Original-Received: via spool by 58558-submit@debbugs.gnu.org id=B58558.1666117177894 (code B ref 58558); Tue, 18 Oct 2022 18:20:01 +0000 Original-Received: (at 58558) by debbugs.gnu.org; 18 Oct 2022 18:19:37 +0000 Original-Received: from localhost ([127.0.0.1]:54093 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1okrBg-0000EM-VL for submit@debbugs.gnu.org; Tue, 18 Oct 2022 14:19:37 -0400 Original-Received: from quimby.gnus.org ([95.216.78.240]:41596) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1okrBf-0000E8-Cm for 58558@debbugs.gnu.org; Tue, 18 Oct 2022 14:19:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:Date:References: In-Reply-To:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=u1CoVgVvBECV8wRDRZlJgVJgy0k7vaincSvs+f2BHGI=; b=fG4CMoZtDCGn1RLZnfcI3YmxMY xTKNkDm5Y/IWtlP/HZGqXJV8t51nsx6K4NMjhXsK3yP3nnAV0/pfY834WeSc9GZvhSMV02ShVvFZo e4cS2bSML8cYvNhlXS/7dGAmVOKZy372WzgzokAjco/hdhWmclkAULw4aQ4CaaqLdeeM=; Original-Received: from [84.212.220.105] (helo=downe) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1okrBV-0005SL-EP; Tue, 18 Oct 2022 20:19:27 +0200 In-Reply-To: <8335bl18lo.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 18 Oct 2022 17:58:59 +0300") Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAAJFBMVEULCgshHh5QT08v Li+Pj4/Q0ND4+Pign55wcHCxsbE/Pj/////9TU4gAAAAAWJLR0QLH9fEwAAAAAd0SU1FB+YKEgsY IudH49YAAAGvSURBVDjLrZJLT8JAEICnLZDiadGIHCsEordWItFbYyJnYkKRGyId4IbxdW2iEI8m RIz/1t3u7HZBuDmH7WS+eXQeAFpKmVRrpcwOVgaagQm4MAoEi2XGg2YgSQo1sK8RsfeWJSV7JcL+ 6xfiI8WoVC6Oj0W2OT5YWTXOVxPyqMeeCc6nulZ7Yvykg6HWbUwycGh6tYaZvgoNYKOvVHfKnxNd ZfGptMK9iJJ+RwkUda5FSMAKWKsDTqxAxOgpYhzxPCtqZW+qaC5CnAE0ZhLkhjosj6KjckeCoqgN KJ4yj2Bk4G4DMa20YouP3qMUFEmg99P1wKVBlEVD1ncK0uy2CaTse2ugA+uiUhU2gSqev9sA6e8y 6VD3DVAYSGCPjVG7SxqJGAQyyKsdiv29eATaCd+63LQTJTR2Acq8emOcbnAx4rUnCrhj4ToKwJmL wEZHAeDxkEPsIi7FLfkapBdTeca+uGm6JSYvJtFNOFGYfmVjjZEGSvXJ7YbslyqYRpHDW5HUOhXl TcA946eP9whVpAZwwU8H4yv4A8A6q9YYbAEbsgtY/wrYLhCUtiHH/wX511YbTcUDIgAAACV0RVh0 ZGF0ZTpjcmVhdGUAMjAyMi0xMC0xOFQxMToyNDozNCswMDowMNjAwoAAAAAldEVYdGRhdGU6bW9k aWZ5ADIwMjItMTAtMThUMTE6MjQ6MzQrMDA6MDCpnXo8AAAAAElFTkSuQmCC X-Now-Playing: Tuff City Kids's _#savefabric (10) (Mixed by Terry Francis)_: "Edlost" X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:245822 Archived-At: Eli Zaretskii writes: >> I briefly tried to use "perf" under Linux to connect to a running >> Emacs and get some data out of it, but... er... I've never used it >> before, and... >> >> Does anybody have a recipe for how to do runtime function tracing for a >> running process? > > The way I run perf is to start Emacs under perf to begin with. > > What did you try? It was quite simple, AFAIR, last time I tried. I thought it might be easier to see the differences in results if one first attached perf to a fresh (fast) Emacs and got the trace, and the waited until Emacs got slow, and repeated the same thing under another trace. perf is able to do this by: perf record -p -g and perf report then shows me stuff, but I don't even know what to look for when interpreting that. Or whether perf is, indeed, the right too for this task.