From: Petteri Hintsanen <petterih@iki.fi>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : Passing buffers to function in elisp
Date: Mon, 27 Feb 2023 22:44:43 +0200 [thread overview]
Message-ID: <87v8jmkfd0.fsf@iki.fi> (raw)
In-Reply-To: jwvk005mhmk.fsf-monnier+emacs@gnu.org
Stefan Monnier via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:
>> If `emms-info-native--read-and-decode-ogg-page' is called very often
>> (hundreds of times or more), it's probably better to use one single
>> buffer instead of a fresh temp buffer every single time.
I tried this and, for a moment, I _think_ it shaved off something like
20-25% of the memory usage (according to the memory profiler). That
would be a big win.
Sadly enough, it was just for a moment, because I cannot replicate it
anymore. It wasn't a particularly controlled setup, so probably I just
messed up something at some point. Nonetheless, using a persistent
buffer seems to be the right thing to do, and seeing how many
" *foo-bar-baz*" buffers there are, it even looks like a pattern.
Also, if I interpreted profiler's hieroglyphs correctly, it told me that
this setq
(setq stream (vconcat stream (plist-get page :stream)))
is a pig -- well, of course it is. I'm accumulating byte vector by
copying its parts. Similarly bindat consumes a lot of memory.
I think I can replace vectors with strings, which should, according to
the elisp manual, "occupy one-fourth the space of a vector of the same
elements." And I guess that accumulation would be best done with a
buffer, not with strings or vectors.
But bindat internals are beyond me.
> That's definitely something to consider. Another is whether the ELisp
> code was byte-compiled (if not, then all bets are off, the interpreter
> itself generates a fair bit of garbage, especially if you use a lot of
> macros).
No, it was not byte-compiled. I don't know how many macros there are.
Just by hand-waving I'd say "not that many". But again what bindat does
is beyond me.
I'll try byte-compiling after the code is in good enough shape to do
controlled experiments.
> Are you using `bindat-type`?
No, not yet. I have been thinking about it, not only because the
current implementation is riddled with ugly evals and kludges, but I
want to save the kittens ;-D
I also need to discuss with EMMS maintainer whether using Emacs 28+
feature is okay.
Thanks to all for insights, I learned a lot.
Petteri
next prev parent reply other threads:[~2023-02-27 20:44 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
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 [this message]
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=87v8jmkfd0.fsf@iki.fi \
--to=petterih@iki.fi \
--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).