unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Petteri Hintsanen <petterih@iki.fi>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Passing buffers to function in elisp
Date: Wed, 06 Sep 2023 17:12:27 -0400	[thread overview]
Message-ID: <jwvtts7nh9k.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <x2m8r9j5dhy.fsf_-_@iki.fi> (Petteri Hintsanen's message of "Wed,  06 Sep 2023 22:05:13 +0300")

>> This is a typical a source of unnecessary O(N²) complexity: the above
>> line takes O(N) time, so if you do it O(N) times, you got your
>> N² blowup.  You're usually better off doing
[...]
> I replaced vconcat with push.  However it did not have a significant
> effect (measured with Emacs memory profiler).  Perhaps the chunks were
> quite small after all.

That's usually the case, indeed.

> In complexity speak, with small N one usually
> does not need to worry about quadratics.

But: it's rare to be sure that N will *always* be small :-(

> I also tried to replace with-temp-buffer forms (such forms are called
> hundreds of times) with a static buffer for holding temporary data.  It
> produced mixed results.  In some limited settings, memory savings were
> considerable, but in some others cases it blew up memory usage.  I
> cannot explain why that happened.  But it seems safest to stick to
> with-temp-buffer.

`with-temp-buffer` is fairly costly, but to the extent that it's pretty
much a constant cost it shouldn't [known on wood] bring surprises in
unexpected circumstances, so if it's fast enough it's a good choice.


        Stefan




  reply	other threads:[~2023-09-06 21:12 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
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 [this message]
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=jwvtts7nh9k.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@gnu.org \
    --cc=petterih@iki.fi \
    /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).