From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: MPS: dangling markers Date: Sat, 29 Jun 2024 15:17:22 +0000 Message-ID: <87v81rg4n1.fsf@localhost> References: <87v81u85hv.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20571"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, Gerd =?utf-8?Q?M=C3=B6llmann?= , Eli Zaretskii , eller.helmut@gmail.com To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 29 17:16:36 2024 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 1sNZoZ-0005AM-Td for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Jun 2024 17:16:36 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sNZnr-0001Xi-6v; Sat, 29 Jun 2024 11:15:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sNZnp-0001XV-13 for emacs-devel@gnu.org; Sat, 29 Jun 2024 11:15:49 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sNZnn-0000CH-6O for emacs-devel@gnu.org; Sat, 29 Jun 2024 11:15:48 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id BFE29240028 for ; Sat, 29 Jun 2024 17:15:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1719674144; bh=I0MwLkqlaIQqRUXN2DtNNkMGcWAkxBChnB76Nt6T+iE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=orXoo3c/u3afw1+ZuDiKF5UDY0/bTugcUPN9BcSOHc2mfXqmLJ3MBddtMKcBXV1br oYzjfcWrFST4iHM9rsErZ3ZY1/lVU3gdO6ZmuXIdNmhqsgNA6DwxfZKYfIQgf6AtXY vkszR01a+kDxnbr5oYHvpIftVpe5tmzkoZYu6NC4+lvitU4k8DgvUhOl8drlmnSSxj FdtyCiYgNYGVayYsP5ZBT1X2x6mdGCH2GpcNClqoh+Wtd+7JPqIVl49istxA/DyiQW 5Ey3qY+eJ7QbEQMvsgYcV1533aU3x9oeYgJQHMbl5NfhktvsM4C5ZFf/oMpxeZRQsO Xff2Ty55HehUw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4WBG8b4ZFMz6tw4; Sat, 29 Jun 2024 17:15:43 +0200 (CEST) In-Reply-To: Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:320858 Archived-At: Stefan Monnier writes: >> - perf points to (1) itree lookup; (2) bytepos<->charpos, which implies >> that things may be related to the number of allocated markers and >> overlays... > ... > So I'm not surprised by your point (2) above, but I don't have an > explanation for your point (1), OTOH. (1) was a false alarm (kind of). The perf recording was for redisplay that did a lot of text property searches. These searches were iterating over the overlays as well, but it had nothing to do with scratch/igc branch; just a normal (slow) redisplay behavior when there are large chunks of hidden text. It's just that igc fiddling with markers made the performance completely unbearable. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at