From: Damien Mattei <damien.mattei@gmail.com>
To: guile-user <guile-user@gnu.org>
Subject: Re: Speed difference between Guile and Racket (and Python)
Date: Sun, 6 Nov 2022 23:35:17 +0100 [thread overview]
Message-ID: <CADEOade6h=VcmjmPF+AH4A_iwzTtd+oztrbub=pNqR4fOrDwqw@mail.gmail.com> (raw)
In-Reply-To: <9F0C43DE-7216-4AB1-ADB9-E9CB80628FC3@telia.com>
at some point, threads block or even crash but the sequential run is slow
too compared to Racket one.
On Sun, Nov 6, 2022 at 11:23 PM Hans Åberg <haberg-1@telia.com> wrote:
>
> > On 6 Nov 2022, at 17:01, Damien Mattei <damien.mattei@gmail.com> wrote:
> >
> > So now the question is why is Guile slow compared to Racket?
>
> How is thread performance? —The Boehm GC puts locks around every memory
> allocation, which is slow if heavy in use.
>
>
next prev parent reply other threads:[~2022-11-06 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 16:01 speed difference between Guile and Racket (and Python) Damien Mattei
2022-11-06 22:23 ` Speed " Hans Åberg
2022-11-06 22:35 ` Damien Mattei [this message]
2022-11-07 9:21 ` speed " Dr. Arne Babenhauserheide
2022-11-07 13:23 ` Zelphir Kaltstahl
2022-11-09 14:24 ` Damien Mattei
2022-11-08 8:03 ` Linus Björnstam
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='CADEOade6h=VcmjmPF+AH4A_iwzTtd+oztrbub=pNqR4fOrDwqw@mail.gmail.com' \
--to=damien.mattei@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).