unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : Passing buffers to function in elisp
Date: Sat, 25 Feb 2023 07:40:48 +0100	[thread overview]
Message-ID: <Y/mtcNOp+8w40Wgi@tuxteam.de> (raw)
In-Reply-To: <87bklihln8.fsf@iki.fi>

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]

On Fri, Feb 24, 2023 at 10:08:11PM +0200, Petteri Hintsanen wrote:
> <tomas@tuxteam.de> writes:
> 
> > On Tue, Feb 21, 2023 at 11:21:47PM +0000, Drew Adams wrote:
> >> What is it that you're really trying to do?
> >
> > That's exactly the point, yes.
> 
> Specifics, as usual, are somewhat messy.  But I try to summarize below.

[...]

Thanks for this very interesting dive :)

It seems you so deeper in the rabbit hole that my general handwaving
doesn't do justice to it.

I'd suggest to call `garbage-collect' explicitly from some
strategic point in your code will tell you what kinds (and
how many) of objects have been collected. You could then at
least have a rough idea on where to focus your efforts (are
the many buffers killing you -- or rather loads and loads
of small cons pairs? Or those many vectors?)

There are many knobs and variables to "look into" what the
garbage collector is thinking, see "Garbage Collection" and
"Memory Usage" in Appendix E of the Elisp manual (the Web
version is here [1], if you prefer that).

Thanks for hacking :-)

Cheers

[1] https://www.gnu.org/software/emacs/manual/html_node/elisp/GNU-Emacs-Internals.html
- 
tomás

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2023-02-25  6:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 21:18 Passing buffers to function in elisp Petteri Hintsanen
2023-02-21 23:21 ` [External] : " Drew Adams
2023-02-22  5:35   ` tomas
2023-02-24 20:08     ` Petteri Hintsanen
2023-02-25  6:40       ` tomas [this message]
2023-02-25 11:23       ` Michael Heerdegen
2023-02-25 13:45         ` tomas
2023-02-25 18:31           ` Michael Heerdegen
2023-02-25 19:05             ` tomas
2023-02-25 23:52         ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-02-27 20:44           ` Petteri Hintsanen
2023-02-28  5:37             ` tomas
2023-03-03 15:19             ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-03-07 21:48               ` Petteri Hintsanen
2023-03-07 22:45                 ` Stefan Monnier
2023-03-08  5:38                   ` tomas
2023-09-06 19:05               ` Petteri Hintsanen
2023-09-06 21:12                 ` Stefan Monnier
2023-02-22  5:30 ` tomas
2023-02-23  9:34   ` Michael Heerdegen
2023-02-23  9:51     ` tomas
2023-02-23 16:19     ` Marcin Borkowski

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=Y/mtcNOp+8w40Wgi@tuxteam.de \
    --to=tomas@tuxteam.de \
    --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).