From: Amirouche Boubekki <amirouche.boubekki@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: Guile User <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: GNU Guile 2.9.7 Released [beta]
Date: Sun, 15 Dec 2019 10:27:29 +0100 [thread overview]
Message-ID: <CAL7_Mo9vD44TOZG5QnaUE35_BaWFoahcEUbPdqUwNg0tuUurEQ@mail.gmail.com> (raw)
In-Reply-To: <CAL7_Mo-nhV7knnNrvksU5OYxRio=5Zc6MUxaymYim9O9qQh8Fw@mail.gmail.com>
Le sam. 14 déc. 2019 à 19:03, Amirouche Boubekki
<amirouche.boubekki@gmail.com> a écrit :
>
> Le ven. 13 déc. 2019 à 14:31, Andy Wingo <wingo@pobox.com> a écrit :
> >
> > We are pleased to announce GNU Guile release 2.9.7. This is the seventh
> > and hopefully next-to-last pre-release of what will eventually become
> > the 3.0 release series.
>
> I tested with nomunofu v0.2.0 (http://hyper.dev/nomunofu-v0.2.0.tar.gz)
>
> The import process is 2% faster using Guile 2.9.7 compared to Guile 2.9.6.
>
> The import process is between 3 and 4 times slower a similar database
> written in C called 4store. The import process is 5 times slower than
> Virtuoso.
>
> Those tests were done against a test file that is much smaller than memory.
I did some tests against more data around 5GB with 32GB of RAM available.
The query with a cold cache is much faster using guile:
cold cache: 0.027838s
hot cache: 0.023536s
The timings for virtuoso with the same query on first start:
cold cache: 0.744s
hot cache: 0.008s
After restarting virtuoso, I got the following timings for the same query:
first query: 0.058s
second query: 0.008s
In the case the cache is cold, the query is 27 times faster with guile
nomunofu. After restarting virtuoso, guile-nomunofu first query is two
times faster.
Disclaimer: benchmarking is a dark art, take those numbers with a grain of salt.
--
Amirouche ~ https://hyper.dev
prev parent reply other threads:[~2019-12-15 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 13:30 GNU Guile 2.9.7 Released [beta] Andy Wingo
2019-12-13 13:50 ` Matt Wette
2019-12-14 14:50 ` Thomas Morley
2019-12-13 16:34 ` Jérémy Korwin-Zmijowski
2019-12-14 2:23 ` John Cowan
2019-12-14 7:40 ` tomas
2019-12-14 18:03 ` Amirouche Boubekki
2019-12-15 9:27 ` Amirouche Boubekki [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=CAL7_Mo9vD44TOZG5QnaUE35_BaWFoahcEUbPdqUwNg0tuUurEQ@mail.gmail.com \
--to=amirouche.boubekki@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.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).