all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: arthur.miller@live.com, emacs-devel@gnu.org
Subject: Re: Emacs memory usage
Date: Wed, 25 Nov 2020 17:27:30 +0200	[thread overview]
Message-ID: <83o8jlsbh9.fsf@gnu.org> (raw)
In-Reply-To: <X73yXXvXSybjk/pR@protected.rcdrun.com> (message from Jean Louis on Wed, 25 Nov 2020 08:57:49 +0300)

> Date: Wed, 25 Nov 2020 08:57:49 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: arthur miller <arthur.miller@live.com>, emacs-devel@gnu.org
> 
> If you think that vsize is pointer to the problem and that we shall
> track visually what do we do that it starts increasing, maybe I could
> make a function that logs what we do. Those major commands. Is there
> some way to log the major commands?

This is probably a good idea.  You can take a snapshot of the value
returned by recent-keys from time to time, and then convert them to
human-readable form by using code similar to what view-lossage does.



  reply	other threads:[~2020-11-25 15:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 14:39 Emacs memory usage Arthur Miller
2020-11-24 14:49 ` Stefan Monnier
2020-11-24 15:08   ` Arthur Miller
2020-11-24 16:12 ` Eli Zaretskii
2020-11-24 22:06   ` Tomas Hlavaty
2020-11-25  3:31     ` Eli Zaretskii
2020-11-25 20:08       ` Tomas Hlavaty
2020-11-25  0:38   ` arthur miller
2020-11-25  3:27     ` Eli Zaretskii
2020-11-25  5:57       ` Jean Louis
2020-11-25 15:27         ` Eli Zaretskii [this message]
2020-11-25 16:01           ` Arthur Miller
2020-11-29  1:30             ` debug-warn macro [was: Re: Emacs memory usage] Adam Porter
2020-11-29  9:42               ` Stefan Kangas
2020-11-29 17:49                 ` Adam Porter
2020-11-24 21:16 ` Emacs memory usage Tomas Hlavaty
2020-11-24 21:53   ` Stefan Monnier
2020-11-25  0:24     ` arthur miller
2020-11-25  0:32   ` arthur miller

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=83o8jlsbh9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=arthur.miller@live.com \
    --cc=bugs@gnu.support \
    --cc=emacs-devel@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.
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.