unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Olivier Dion via General Guile related discussions <guile-user@gnu.org>
To: guile-user@gnu.org
Subject: Looking for a computation benchmark in Guile
Date: Thu, 10 Nov 2022 13:35:02 -0500	[thread overview]
Message-ID: <87fseqodyh.fsf@laura> (raw)

Hi,

In my research on dynamic instrumentation, I would like to see what's
the runtime overhead of dynamically patching function entry/exit with my
tool.  I can already patch every libguile function dynamically, I just
need to see what's the impact on the runtime now.

Here's the specification of such benchmark:

 1. No I/O
 2. No delimited computation (no rewind of the stack)
 3. No foreign call
 4. Can be multi-thread (would be great actually)
 5. Reproducible (pure computation are great candidate)

Also, maybe there's already standardized benchmark also for Scheme.  If
so a link to them or an implementation in Guile would be awesome.

If you have a scenario like that, please contact me!

-- 
Olivier Dion
oldiob.dev




             reply	other threads:[~2022-11-10 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 18:35 Olivier Dion via General Guile related discussions [this message]
2022-11-10 20:37 ` Looking for a computation benchmark in Guile Dr. Arne Babenhauserheide

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=87fseqodyh.fsf@laura \
    --to=guile-user@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    /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).