From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: guile-devel@gnu.org
Subject: Re: Increasing default initial heap size?
Date: Sun, 21 Aug 2022 00:57:50 +0200 [thread overview]
Message-ID: <871qtabjhx.fsf@web.de> (raw)
In-Reply-To: <875yimbtds.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
"Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
> With the original setting, most benchmarks take around 4-6 MB of
> memory.
> - x1: 4-6 MB
> - x2: 6-9 MB
> - x3: 4-10 MB
> - x4: ~11 MB
> - x32: 4-74 MB
Additional support to the comment by Andy about heap size:
racket -e "(sleep 30)"
This takes 117.5 MB.
guile -c "(sleep 30)"
This takes 2.9 MB.
The interactive Guile REPL takes 17 MB.
The interactive Chez REPL takes 18 MB.
Chez not taking much more memory despite being faster says something
about the speed of Chez …
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
prev parent reply other threads:[~2022-08-20 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 12:24 Increasing default initial heap size? Dr. Arne Babenhauserheide
2022-08-20 22:57 ` Dr. Arne Babenhauserheide [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=871qtabjhx.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-devel@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).