[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: igc, macOS avoiding signals
From: |
Helmut Eller |
Subject: |
Re: igc, macOS avoiding signals |
Date: |
Sun, 29 Dec 2024 09:02:27 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
On Sat, Dec 28 2024, Óscar Fuentes wrote:
[...]
> Something related to UI responsiveness would be great. For instance,
> record the time from each interactive command start to command end (or,
> better, until Emacs is idle again, to account for commands accumulating
> on the queue). Then we can perform some statistical analysis on that
> info.
>
> I'm afraid that if we start discussing personal perceptions we will
> devote a lot of time trying to fine-adjust parameters.
I couldn't agree more.
What would you think about using one of those tracing frameworks, like
LTTng[*]? Are those any good?
It would be nice, if those tracing points could be used in normal
everyday sessions. E.g. to see how memory usage evolved over the last
15 minutes or to see if there was a particularly slow regexp search.
Helmut
[*] https://lttng.org/
- Re: igc, macOS avoiding signals, Sean Devlin, 2024/12/28
- Re: igc, macOS avoiding signals, Gerd Möllmann, 2024/12/28
- Re: igc, macOS avoiding signals, Eli Zaretskii, 2024/12/28
- Re: igc, macOS avoiding signals, Gerd Möllmann, 2024/12/28
- Re: igc, macOS avoiding signals, Gerd Möllmann, 2024/12/30
- Re: igc, macOS avoiding signals, Gerd Möllmann, 2024/12/30
- Re: igc, macOS avoiding signals, Helmut Eller, 2024/12/30
- Re: igc, macOS avoiding signals, Gerd Möllmann, 2024/12/30
- Re: igc, macOS avoiding signals, Helmut Eller, 2024/12/30
- Re: igc, macOS avoiding signals, Gerd Möllmann, 2024/12/30