all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>,
	Evan Cooney <evancooney71@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Including code in a non-Guile language into Guix
Date: Tue, 10 Dec 2024 17:24:50 +0100	[thread overview]
Message-ID: <87pllzy08d.fsf@gmail.com> (raw)
In-Reply-To: <87zfmkl048.fsf@elephly.net>

Hi,

On Thu, 31 Oct 2024 at 17:15, Ricardo Wurmus <rekado@elephly.net> wrote:

>> by rewriting some of the
>> code in a more performance-oriented language like C?
>
> No.
>
> Guile is not the bottleneck.

For what it is worth, some months ago I gave a look to ’sort’.

The current implementation provided by Guile is written in C.  Guess
what?  I wrote some pure Guile as fast as such C (if not faster!).

https://simon.tournier.info/posts/2024-02-05-guile-sort/index.html

To make explicit my understanding of Ricardo’s answer: no it’s not the
Scheme compiler provided by Guile that is the current performance
bottleneck but there is still room of improvement for the whole Guile
(Garbage Collection, Standard Library, etc.).

Cheers,
simon


  reply	other threads:[~2024-12-10 16:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31  2:34 Including code in a non-Guile language into Guix Evan Cooney
2024-10-31 12:31 ` Daniel Littlewood
2024-10-31 14:15   ` Suhail Singh
2024-10-31 16:13     ` Ricardo Wurmus
2024-10-31 17:12       ` Suhail Singh
2024-10-31 16:15     ` Runciter via Development of GNU Guix and the GNU System distribution.
2024-10-31 16:23       ` Evan Cooney
2024-12-10 16:30   ` Simon Tournier
2024-10-31 16:15 ` Ricardo Wurmus
2024-12-10 16:24   ` Simon Tournier [this message]
2024-12-15 12:22     ` Maxim Cournoyer
2024-11-01 22:49 ` Attila Lendvai

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pllzy08d.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=evancooney71@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.