unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Observing lags or never ending processes
Date: Mon, 19 Sep 2022 22:01:06 +0300	[thread overview]
Message-ID: <83edw7xk7h.fsf@gnu.org> (raw)
In-Reply-To: <Yyi4bcsGrKgt4QTH@protected.localdomain> (message from Jean Louis on Mon, 19 Sep 2022 21:43:57 +0300)

> Date: Mon, 19 Sep 2022 21:43:57 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: help-gnu-emacs@gnu.org
> 
> > But if GC is responsible for those "lags", then it's normal Emacs
> > operation, and you should look into changing your use patterns and
> > packages you load so as to make the memory footprint of your Emacs
> > sessions smaller, preferably so that it is never swapped out of
> > physical memory.  If you customized the GC threshold to a much higher
> > value, lower it.  Or maybe you have some other memory-intensive
> > programs on your system that create situations where some of Emacs's
> > memory is swapped out.  These are all reasons for GC being much slower
> > than it's supposed to be.
> 
> How exactly can I change use patterns?

How should I know?  I don't even know what are your present use
patterns, which packages you routinely load, which ones you use
frequently, how many buffers are typically present in your session,
etc. etc.

> Today I was waiting 1 hour for garbage collection, two times, before I
> killed Emacs.

Did you change the GC thresholds?  (I asked that above, but you didn't
answer.)



  reply	other threads:[~2022-09-19 19:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11  6:59 Observing lags or never ending processes Jean Louis
2022-09-11  7:06 ` Eli Zaretskii
2022-09-11 12:36   ` Jean Louis
2022-09-11 13:16     ` Eli Zaretskii
2022-09-11 13:31       ` Jean Louis
2022-09-11 20:21       ` Jean Louis
2022-09-12  2:26         ` Eli Zaretskii
2022-09-12  5:53           ` Jean Louis
2022-09-12 11:19             ` Eli Zaretskii
2022-09-12 12:35               ` Jean Louis
2022-09-12  7:50           ` Jean Louis
2022-09-12 11:32             ` Eli Zaretskii
2022-09-16 19:06       ` Jean Louis
2022-09-17  6:00         ` Eli Zaretskii
2022-09-19 18:43           ` Jean Louis
2022-09-19 19:01             ` Eli Zaretskii [this message]
2022-09-20  4:42               ` Jean Louis
2022-09-20  7:54                 ` Emanuel Berg
2022-09-22 20:30                   ` Jean Louis
2022-09-23  5:30                     ` Jean Louis
2022-09-23  6:13                     ` Eli Zaretskii
2022-09-23  8:17                       ` Jean Louis
2022-09-23 10:42                         ` Eli Zaretskii
2022-09-23 14:16                           ` Jean Louis
2022-09-24 15:30                             ` Emanuel Berg
2022-09-23 11:30                     ` Emanuel Berg
2022-09-20 11:20                 ` Eli Zaretskii
2022-09-20 18:17                   ` Emanuel Berg
2022-09-19 23:11             ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-09-11 15:57   ` Jean Louis

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83edw7xk7h.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).