From: Brendan Tildesley <mail@brendan.scot>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: SHA256 performance with Guile 2.2 vs. Guile 3.0
Date: Sat, 4 Jan 2020 17:21:42 +1100 [thread overview]
Message-ID: <f6dd29bd-deb6-ac8b-21a5-3e24a45708b4@brendan.scot> (raw)
> Still far from the libgcrypt implementation in C + asm, but hey!
Actually guix hash is still a lot slower than using the sha256sum cli
tool. For me 7x faster for the guile tarball, and 4x faster for a 700MiB
file. Maybe because guile opens a file with it's ports and feeds it to
libgcrypt. If guix is heavy relying on hashing files stored in the
filesystem, maybe it would be better to directly use sha256sum or
perhaps libgcrypt has a function do open a file and hash it on it's own?
next reply other threads:[~2020-01-04 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 6:21 Brendan Tildesley [this message]
2020-01-08 21:20 ` SHA256 performance with Guile 2.2 vs. Guile 3.0 Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f6dd29bd-deb6-ac8b-21a5-3e24a45708b4@brendan.scot \
--to=mail@brendan.scot \
--cc=guix-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).