From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Some experience with the igc branch Date: Sun, 22 Dec 2024 20:11:17 +0100 Message-ID: <87h66vwn1m.fsf@telefonica.net> References: <87o713wwsi.fsf@telefonica.net> <87ldw7fwet.fsf@protonmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19814"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Pip Cet , Gerd =?utf-8?Q?M=C3=B6llmann?= , Helmut Eller , Andrea Corallo To: Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 22 20:12:29 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 1tPRNN-00053W-L9 for ged-emacs-devel@m.gmane-mx.org; Sun, 22 Dec 2024 20:12:29 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tPRMf-000208-Bk; Sun, 22 Dec 2024 14:11:45 -0500 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 1tPRMV-0001zd-29 for emacs-devel@gnu.org; Sun, 22 Dec 2024 14:11:36 -0500 Original-Received: from relayout04.e.movistar.es ([86.109.101.204] helo=relayout04-redir.e.movistar.es) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tPRMQ-0004TI-7h; Sun, 22 Dec 2024 14:11:33 -0500 Original-Received: from sky (26.red-81-39-22.dynamicip.rima-tde.net [81.39.22.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: 981711563@telefonica.net) by relayout04.e.movistar.es (Postfix) with ESMTPSA id 4YGW394QtNz16RfZ; Sun, 22 Dec 2024 20:11:17 +0100 (CET) In-Reply-To: <87ldw7fwet.fsf@protonmail.com> (Pip Cet via's message of "Sun, 22 Dec 2024 17:41:47 +0000") X-TnetOut-Country: IP: 81.39.22.26 | Country: ES X-TnetOut-Information: AntiSPAM and AntiVIRUS on relayout04 X-TnetOut-MsgID: 4YGW394QtNz16RfZ.A5ED2 X-TnetOut-SpamCheck: no es spam, clean X-TnetOut-From: ofv@wanadoo.es X-TnetOut-Watermark: 1735499478.13665@xNVBX+M8s8Uj34BDrrWy4w Received-SPF: softfail client-ip=86.109.101.204; envelope-from=ofv@wanadoo.es; helo=relayout04-redir.e.movistar.es X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665 autolearn=no 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:326879 Archived-At: Pip Cet via "Emacs development discussions." writes: >> I suspect that some of those >> pauses are not related to garbage collection (executing code and moving >> data also takes time.) > > Quite possible. Even if it is GC, please keep in mind that MPS has many > settings which you can play with, and it can improve things a lot. It's > not too early to become a fan of the scratch/igc branch, but it is too > early to reject it for performance reasons. It's a "heads you lose, tails I > win" situation, I guess. IIRC MPS is well documented and I can look up those settings, but does Emacs collect the required info for taking informed decisions? Anyway, with the setup I'm using for this job is totally unrealistic to expect instant reaction from Emacs, there is too much heavy stuff kicking in for every keypress. > 1. The signal issue. I don't have a good way to fix this and make > everyone happy, but I do have a solution which hasn't caused a crash for > me in quite a while. It may be good enough. Inevitably, a few minutes after sending my message Emacs froze after working flawlessly since you fixed the JSON issue. Redisplay just stopped while showing the menu, no crash nor infinite loop, its CPU usage was typical for the repeating timers that my config creates. Sadly, instead of attaching gdb I tried to wake up Emacs by sending SIGUSR1 (no effect, as it is the wrong signal, should be SIGUSR2) and then sent SINGINT by mistake, which terminated the process. It's very likely that MPS is innocent on this, but I'm happy to apply and test any stability improvement patch you have and wish to share. Thanks.