From: Maxime Devos <maximedevos@telenet.be>
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>,
guile-devel <guile-devel@gnu.org>
Subject: Re: hastbables in scheme, are they slow? using goops is this madness
Date: Tue, 22 Feb 2022 08:14:13 +0100 [thread overview]
Message-ID: <07c1258b2e3695c065dd3e9ff1dceff2a2eef519.camel@telenet.be> (raw)
In-Reply-To: <CAGua6m1T__jWbDfSnbj=Gx97adaM1a2Npst9LvhvpK_C39SpgA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
Stefan Israelsson Tampe schreef op di 22-02-2022 om 00:05 [+0100]:
> 2. For very large hash tables C based solutions are about 1.5-2.0
> faster.
> (for-each (lambda (i) (hashq-set! h i i)) (iota 20000000))
For what sizes is Scheme faster, and for what sizes is Scheme faster?
Where is the cut-off point?
Also, seems quite nice. While I haven't had noticed performance
problems yet with C hashtables, the Scheme implementation would
eliminate the problem of 'hash-for-each' forming a continuation
barrier.
> LICENSE
> LGPL v2 or v3
Guile is LGPL2+, so to be eventually integrated into Guile, shouldn't
it to LGPL2+ (there might eventually be a LGPLv4)?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2022-02-22 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 23:05 hastbables in scheme, are they slow? using goops is this madness Stefan Israelsson Tampe
2022-02-22 7:14 ` Maxime Devos [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=07c1258b2e3695c065dd3e9ff1dceff2a2eef519.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=stefan.itampe@gmail.com \
/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).