unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Linas Vepstas <linasvepstas@gmail.com>
To: Mike Gran <spk121@yahoo.com>
Cc: Rchar <rchar@protonmail.com>, "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Guile benchmark
Date: Thu, 26 Jan 2017 16:11:56 -0600	[thread overview]
Message-ID: <CAHrUA35QB_fzY8ou+W559TRSRCq5ftd+YQHG0wJ9sxNRo3F3Vw@mail.gmail.com> (raw)
In-Reply-To: <936070038.1608686.1485467787867@mail.yahoo.com>

On Thu, Jan 26, 2017 at 3:56 PM, Mike Gran <spk121@yahoo.com> wrote:

>
> On Thursday, January 26, 2017 7:31 AM, Rchar <rchar@protonmail.com> wrote:
>
>
>> Is Guile slow or fast, comparing to others?
>
> Guile is about average compared to the others. But it depends
> on the specific task. It is usually not the fastest or slowest.

FWIW, I have C++ code that has bindings both to guile and to python,
via cython.  The guile bindings were faster than python, which then
caused the cython maintainer to enter a nuclear arms race, to improve
performance, doing things like caching values in various places to improve
performance.  But then, one can do the same in guile, and it becomes a
game of who can be more clever in optimizing.

I do have one complaint: guile has a fairly hefty overhead in entering
and exiting: I forget now, and the measurements were done on a
circa-2011 PC, but I was getting something like 7K guile enter-exits
per second, which limits the speed at which you can cross the C/guile
boundary.   You can avoid this cost by entering guile and then caching,
but this requires some C-coding cleverness that naive users won't do.
(I'm currently getting maybe 500K/sec or 1M/sec guile-C crossings, but
only if I do this caching trick).

--linas



  reply	other threads:[~2017-01-26 22:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26  8:39 Guile benchmark Rchar
2017-01-26 21:56 ` Mike Gran
2017-01-26 22:11   ` Linas Vepstas [this message]
2017-01-30 14:16 ` Ludovic Courtès
2017-02-27 20:00 ` Andy Wingo
2017-02-27 23:35   ` Chris Vine
2017-02-28 10:28     ` Arne Babenhauserheide
2017-02-28 12:55       ` Chris Vine
2017-03-01  0:24         ` 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=CAHrUA35QB_fzY8ou+W559TRSRCq5ftd+YQHG0wJ9sxNRo3F3Vw@mail.gmail.com \
    --to=linasvepstas@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=rchar@protonmail.com \
    --cc=spk121@yahoo.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).