bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Paul Eggert <eggert@cs.ucla.edu>,
	bug-gnulib@gnu.org, Collin Funk <collin.funk1@gmail.com>
Subject: Re: diffutils __pycache__ failure.
Date: Mon, 22 Apr 2024 22:55:16 +0200	[thread overview]
Message-ID: <5794066.hSnDOejNSh@nimes> (raw)
In-Reply-To: <67624884-98ff-4dfc-a719-8671f1f9b2fd@gmail.com>

Collin Funk wrote:
> >> I have no clue if this has a noticeable performance impact or not.
> > 
> > Can you measure it, please? For example, with
> >   GNULIB_TOOL_IMPL=py time ./test-all.sh
> > 
> > I measure a difference in the 2% range, but it's not clear to me whether
> > -B slows down or speeds up things :)
> 
> Sure, here is the results using the -B flag. I'm removing the
> __pycache__ directory before using -B flag to make sure it doesn't get
> read.
> 
> Using 'env GNULIB_TOOL_IMPL=py ./test-all.sh' in import-tests:
> 
>       no -B flag: 0m16.699s
>       -B flag: 0m20.892s
> 
> Using 'env GNULIB_TOOL_IMPL=py ./test-all.sh' in create-tests:
> 
>       no -B flag: 2m45.046s
>       -B flag: 2m46.674s

Thanks for measuring it. So, the -B flag causes a slowdown.

> The create-tests spend most of their time in autoconf and friends if I
> remember correctly.
> 
> The import tests feel noticeably slower with -B to me.

This is explained by the fact that the import tests do nearly 100
gnulib-tool invocations: The same just-in-time compilation must happen
in memory 100 times. This explains the 4 seconds of slowdown.

Bruno





  reply	other threads:[~2024-04-22 20:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-21 10:52 GNU gnulib: calling for beta-testers Bruno Haible
2024-04-21 11:52 ` Vivien Kraus
2024-04-22  7:56 ` Paul Eggert
2024-04-22  8:23   ` Collin Funk
2024-04-22  8:51     ` diffutils __pycache__ failure Collin Funk
2024-04-22 11:38       ` Bruno Haible
2024-04-22 19:44         ` Collin Funk
2024-04-22 20:55           ` Bruno Haible [this message]
2024-04-22 11:22     ` GNU gnulib: calling for beta-testers Bruno Haible
2024-04-22 20:00       ` Collin Funk
2024-04-22 20:56         ` Bruno Haible

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://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5794066.hSnDOejNSh@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=collin.funk1@gmail.com \
    --cc=eggert@cs.ucla.edu \
    /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).