unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Taylan Kammer <taylan.kammer@gmail.com>
To: guile-devel@gnu.org
Subject: Re: [PATCHES] Use a better SRFI-64 implementation.
Date: Tue, 11 May 2021 16:32:08 +0200	[thread overview]
Message-ID: <abfe8a96-e612-362e-29a3-06b3aef34154@gmail.com> (raw)
In-Reply-To: <94ecc225-684f-1d36-bc72-53b8026753b6@gmail.com>

On 10.05.2021 20:25, Taylan Kammer wrote:
> 
> - Improved expand-time performance for large test suites
> 

I thought it would be a good idea to quantify this, so I
benchmarked the compilation performance of a test suite
of 289 tests (that of the scheme-bytsetructures library),
and had the following results.

The first three compilations are with stock Guile 3.0.7,
and the latter three are with the patch that replaces
the SRFI-64 implementation applied to 3.0.7.


=== snip ===

$ touch run-tests.guile.scm && time /opt/guile-3.0.7/bin/guild compile -L . run-tests.guile.scm 
wrote `.../run-tests.guile.scm.go'

real	0m9.465s
user	0m12.787s
sys	0m2.179s

$ touch run-tests.guile.scm && time /opt/guile-3.0.7/bin/guild compile -L . run-tests.guile.scm 
wrote `.../run-tests.guile.scm.go'

real	0m9.419s
user	0m12.988s
sys	0m1.842s

$ touch run-tests.guile.scm && time /opt/guile-3.0.7/bin/guild compile -L . run-tests.guile.scm 
wrote `.../run-tests.guile.scm.go'

real	0m9.387s
user	0m13.132s
sys	0m1.656s

$ touch run-tests.guile.scm && time /opt/guile-master/bin/guild compile -L . run-tests.guile.scm 
wrote `.../run-tests.guile.scm.go'

real	0m4.371s
user	0m5.903s
sys	0m1.239s

$ touch run-tests.guile.scm && time /opt/guile-master/bin/guild compile -L . run-tests.guile.scm 
wrote `.../run-tests.guile.scm.go'

real	0m4.556s
user	0m6.836s
sys	0m1.502s

$ touch run-tests.guile.scm && time /opt/guile-master/bin/guild compile -L . run-tests.guile.scm 
wrote `.../run-tests.guile.scm.go'

real	0m4.493s
user	0m6.273s
sys	0m1.767s

=== /snip ===


As you can see, the time to compile the test suite is cut in half.


Here's the test suite used for the benchmark:

https://github.com/TaylanUB/scheme-bytestructures/blob/master/run-tests.body.scm

(That file is included from run-test.guile.scm.)


- Taylan



  parent reply	other threads:[~2021-05-11 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 18:25 [PATCHES] Use a better SRFI-64 implementation Taylan Kammer
2021-05-11 11:32 ` Taylan Kammer
2021-05-11 19:14   ` Taylan Kammer
2021-05-11 20:52     ` Taylan Kammer
2021-05-11 14:32 ` Taylan Kammer [this message]
2021-05-11 19:39 ` Taylan Kammer

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=abfe8a96-e612-362e-29a3-06b3aef34154@gmail.com \
    --to=taylan.kammer@gmail.com \
    --cc=guile-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.
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).