unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Guile's time execution issues
Date: Sun, 3 May 2020 17:32:29 -0700	[thread overview]
Message-ID: <CA+XASoX8NUiTgwgWq-QBaF16qy8h8EyDk7Om49=y547gyVmF6A@mail.gmail.com> (raw)
In-Reply-To: <87a72q77gr.fsf@gnu.org>

On Sat, May 2, 2020 at 7:11 AM Ludovic Courtès <ludo@gnu.org> wrote:

> Hola!
>
>
Hola!

So weird I'm getting different numbers on 2.2.7. Not sure how I'm getting
those initial ~20s and you are getting consistent ~ 45s. It shouldn't have
nothing to do with it, but could it be I'm running it on macOS?

Now, it would be good to profile ‘json->scm’ to see if there’s anything
> that could be improved on the Guile side, or if it’s just a normal
> profile for GC-intensive code.
>
>
Good news is that I have been working on performance improvements and
json->scm is going down from my ~19 seconds to ~3 seconds on the same
sample file. Linus Björnstam was the one to bring up performance issues so
we've been back and forth trying to make it fast.

One thing I found is that `match` is slow. The code looked nicer but had to
change it back to lets and conds as the performance increase was ~2 seconds.

Thanks for looking into this,

Aleix


  reply	other threads:[~2020-05-04  0:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 22:03 Guile's time execution issues Aleix Conchillo Flaqué
2020-04-22 13:47 ` Linus Björnstam
2020-04-26 17:16 ` Ludovic Courtès
2020-04-26 23:14   ` Aleix Conchillo Flaqué
2020-05-02 14:11     ` Ludovic Courtès
2020-05-04  0:32       ` Aleix Conchillo Flaqué [this message]
2020-05-04  9:36         ` Ludovic Courtès
2020-05-04 11:19           ` Linus Björnstam
2020-05-04 20:09             ` Ludovic Courtès
2020-05-04 20:50               ` Linus Björnstam
2020-05-08 11:31                 ` Linus Björnstam
2020-05-04 18:47           ` Linus Björnstam

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='CA+XASoX8NUiTgwgWq-QBaF16qy8h8EyDk7Om49=y547gyVmF6A@mail.gmail.com' \
    --to=aconchillo@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=ludo@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).