From: Sascha Ziemann <ceving@gmail.com>
To: guile-user@gnu.org
Subject: Re: list vs vector
Date: Thu, 29 Dec 2022 10:43:49 +0100 [thread overview]
Message-ID: <CAGUt3y7UnkoR_LziwNp5KPwpWjt0=iAKLNGNmoVzOchy427yaQ@mail.gmail.com> (raw)
In-Reply-To: <874jtfqnv8.fsf@laura>
> Clearly we're spending way much time in the GC with the vxml variant.
Thanks a lot! This is a nice tutorial for statprof.
What you have found out, was already my guess but I had no proof. The
VXML version does not utilize the fact that the nodes are already
destructured. During each visit of a node, the vector gets converted
into an argument list and the result of the visit is that a new vector
gets created. This produces a lot of garbage. It would be better to
just pass the vector to the visiting function in order to return
itself, if no modification is necessary.
prev parent reply other threads:[~2022-12-29 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 13:22 list vs vector Sascha Ziemann
2022-12-28 14:34 ` tomas
2022-12-28 18:29 ` Damien Mattei
2022-12-28 20:23 ` Olivier Dion via General Guile related discussions
2022-12-29 9:43 ` Sascha Ziemann [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGUt3y7UnkoR_LziwNp5KPwpWjt0=iAKLNGNmoVzOchy427yaQ@mail.gmail.com' \
--to=ceving@gmail.com \
--cc=guile-user@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).