From: Jan Wedekind <jan@wedesoft.de>
To: guile-user@gnu.org
Subject: Garbage collector tuning?
Date: Thu, 10 Sep 2015 07:46:57 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.11.1509100733580.7865@wedemob> (raw)
Hi,
I wonder whether there is a more performant way to allocate larger memory
blocks (e.g. 1 MByte). "gc-malloc-pointerless" seems to be much slower
than "malloc":
user system total real
Guile allocate memory 0.003780 0.000020 0.003800 ( 0.003810)
C allocate memory 0.000060 0.000000 0.000060 ( 0.000070)
Is there a way to control how often the garbage collector is run?
Thanks
Jan
[1] https://github.com/wedesoft/aiscm/blob/master/bench/bench.scm
[2] https://github.com/wedesoft/aiscm/blob/master/bench/cbench.c
next reply other threads:[~2015-09-10 6:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 6:46 Jan Wedekind [this message]
2015-09-10 13:30 ` Garbage collector tuning? Ludovic Courtès
2015-09-10 15:51 ` Stefan Israelsson Tampe
2015-09-10 16:33 ` Jan Wedekind
2015-09-10 17:07 ` Jan Wedekind
2015-09-10 17:54 ` David Pirotte
2015-09-10 21:37 ` Jan Wedekind
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=alpine.DEB.2.11.1509100733580.7865@wedemob \
--to=jan@wedesoft.de \
--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).