[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Some experience with the igc branch
From: |
Gerd Möllmann |
Subject: |
Re: Some experience with the igc branch |
Date: |
Mon, 23 Dec 2024 04:42:17 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Pip Cet <pipcet@protonmail.com> writes:
> Óscar Fuentes <ofv@wanadoo.es> writes:
>
>> Pip Cet via "Emacs development discussions." <emacs-devel@gnu.org>
>> 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?
>
> Not that I'm aware of, at this point.
Me neither.
(And, at least for me personally, "interactive performance", i.e. the
impression a user gets when he's using Emacs interactively, is the only
interesting part. That's difficult to measure of course. I don't care
much about performance improvements I don't notice :-)).
>
>>> 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.
>
> Sorry to hear it, and thanks for letting us know! If it happens again,
> any additional information you can provide would be very helpful.
>
>> 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.
>
> That's a bit odd. It might be the signal issue, but that's purely a
> guess. If it happens again, please let us know.
>
> Which windowing system are you using, and how are you displaying menus,
> though?
Yes. I don't think I've ever seen a freeze caused by igc here. It always
was crashes. But one never knows, of course.
- Re: Some experience with the igc branch, (continued)
- Re: Some experience with the igc branch, Gerd Möllmann, 2024/12/22
- Re: Some experience with the igc branch, Pip Cet, 2024/12/22
- Re: Some experience with the igc branch, Gerd Möllmann, 2024/12/22
- Re: Some experience with the igc branch, Óscar Fuentes, 2024/12/22
- Re: Some experience with the igc branch, Pip Cet, 2024/12/22
- Re: Some experience with the igc branch, Óscar Fuentes, 2024/12/22
- Re: Some experience with the igc branch, Pip Cet, 2024/12/24
- Freezing frame with igc, Gerd Möllmann, 2024/12/24
- Re: Freezing frame with igc, Pip Cet, 2024/12/25
- Re: Freezing frame with igc, Óscar Fuentes, 2024/12/25
- Re: Some experience with the igc branch,
Gerd Möllmann <=
- Re: Some experience with the igc branch, Jean Louis, 2024/12/23
Re: Some experience with the igc branch, Helmut Eller, 2024/12/22
Re: Some experience with the igc branch, Gerd Möllmann, 2024/12/22
- Re: Some experience with the igc branch, Pip Cet, 2024/12/22
- Re: Some experience with the igc branch, Gerd Möllmann, 2024/12/22
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Re: Make Signal handling patch platform-dependent?, Pip Cet, 2024/12/23
- Re: Make Signal handling patch platform-dependent?, Gerd Möllmann, 2024/12/23
- Re: Make Signal handling patch platform-dependent?, Eli Zaretskii, 2024/12/23
Re: Some experience with the igc branch, Eli Zaretskii, 2024/12/23
Discussion with MPS people, Gerd Möllmann, 2024/12/23