all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: execvy@gmail.com
To: Pip Cet <pipcet@protonmail.com>, emacs-devel@gnu.org
Subject: Re: Emacs [scratch/igc 6682d0e6c96] crash on Linux 6.6.41 KDE 6.0.5,  wayland
Date: Tue, 3 Sep 2024 19:20:37 +0800	[thread overview]
Message-ID: <f1990d37-c48d-4324-9dfb-3188d27bc80b@gmail.com> (raw)
In-Reply-To: <87a5gp2ef5.fsf@protonmail.com>

> That's still a very large size for the initial generation, in
particular.  May I ask why you decided to do that? 

When I living in Emacs, I like long press `j` (evil-next-line) and `k` (evil-previous-line) to move around the code.
In master build, long press `j` and `k` are very smooth.
But in mps build, long press `j` and `k` can feel frequent brief pauses. 

So I tested whether increasing the number in `mps_gen_param_s` would make long-pressing `j` and `k` smoother. After the test, it did help, but I still feel pauses when long-pressing `j` and `k`.


> Are we sure that it's GC causing this?  I assume control + right click
shows a buffer menu, so it builds a list of all buffers, and you have a
lot of them...

No, I think the ctrl + right click is not related to GC.




On 9/3/24 6:57 PM, Pip Cet <pipcet@protonmail.com> wrote:
> <execvy@gmail.com> writes:
> 
> > After I change `mps_gen_param_s gens[] = { { 128000, 0.8 }, { 5 * 128000, 0.4 } };`
> > to `mps_gen_param_s gens[] = { { 12800000, 0.8 }, { 5 * 12800000, 0.4 } };`, the Emacs never crash again.
> 
> That's still a very large size for the initial generation, in
> particular.  May I ask why you decided to do that?  I think for
> interactive use, you want to keep the initial generation reasonably
> small.
> 
> > And it's RES mem is 2661M, I think it's good, I'm editing 2000 rust files in Emacs with rust-analyzer lsp server. 99% of time I don't feel GC's lag.
> > But, When I hit `Ctrl + right click`, I feel a very long GC lag ( > 10 seconds). It's reproducible.
> 
> Are we sure that it's GC causing this?  I assume control + right click
> shows a buffer menu, so it builds a list of all buffers, and you have a
> lot of them...
> 
> I've played around a little creating 10,000 buffers and showing the
> buffer menu, and there does appear to be some lag, but this is true both
> with and without MPS.  I also tried a build with --with-x-toolkit=no,
> and that seemed to have less lag.
> 
> > So I profiler-start, then `Ctrl + right click`, then `profiler-stop`, got:
> > ```
> >         14726  58%   Automatic GC
> >         10528  41% - help-command-error-confusable-suggestions
> >         10528  41%  - debug
> >         10528  41%   - recursive-edit
> >           391   1%    - substitute-command-keys
> 
> I cannot tell from this whether MPS was called once and took a very long
> time to run, or was called many times and the problem lies elsewhere.
> 
> Does the problem happen with the default generation sizes?
> 
> Pip
> 
> 



      reply	other threads:[~2024-09-03 11:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02 12:24 Emacs [scratch/igc 6682d0e6c96] crash on Linux 6.6.41 KDE 6.0.5, wayland Eval Exec
2024-09-02 13:06 ` Eli Zaretskii
2024-09-02 13:08   ` Eval EXEC
2024-09-02 16:41 ` Pip Cet
2024-09-03  1:10   ` execvy
2024-09-03  3:33     ` Eval EXEC
2024-09-03 12:58       ` Eli Zaretskii
2024-09-03 14:58         ` execvy
2024-09-03 15:34           ` Eli Zaretskii
2024-09-03 15:57             ` Pip Cet
2024-09-03 16:06               ` Eli Zaretskii
2024-09-03 16:22                 ` Eval EXEC
2024-09-03 17:36                   ` Eli Zaretskii
2024-09-03 10:57     ` Pip Cet
2024-09-03 11:20       ` execvy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f1990d37-c48d-4324-9dfb-3188d27bc80b@gmail.com \
    --to=execvy@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=pipcet@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.