From: Simon Josefsson via Gnulib discussion list <bug-gnulib@gnu.org>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: beta-tester call draft
Date: Sat, 20 Apr 2024 11:38:26 +0200 [thread overview]
Message-ID: <878r18fk6l.fsf@kaka.sjd.se> (raw)
In-Reply-To: <17575364.8ZXASUQcjA@nimes> (Bruno Haible's message of "Sat, 20 Apr 2024 02:22:28 +0200")
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
Bruno Haible <bruno@clisp.org> writes:
> Hi,
>
> It's now time to call for beta-testers of the Python gnulib-tool.
> I plan to post the same text to info-gnu and to planet.gnu.org.
Confirmed success with oath-toolkit; identical generated files.
Old execution time was ~48 seconds, now it is at 0.7 seconds.
The slow gnulib-tool runtime was the primary reason for putting gnulib
generated files into git for oath-toolkit. Waiting close to a minute
for a fresh rebuild became unbearable during development cycles, and
this is not on the slowest of machines (i7-1260P, 64GB RAM, Samsung SSD
990 PRO). Now I can experiment with removing gnulib files from version
control again.
jas@kaka:~/src/oath-toolkit$ time make -f cfg.mk
...
real 0m48,169s
user 0m49,900s
sys 0m9,658s
jas@kaka:~/src/oath-toolkit$ export GNULIB_TOOL_IMPL=py
jas@kaka:~/src/oath-toolkit$ time make -f cfg.mk
...
real 0m0,704s
user 0m0,527s
sys 0m0,179s
jas@kaka:~/src/oath-toolkit$
In case you doubt this was due to a caching speedup, here is another
invocation right after the previous python run:
jas@kaka:~/src/oath-toolkit$ export GNULIB_TOOL_IMPL=sh
jas@kaka:~/src/oath-toolkit$ time make -f cfg.mk
...
real 0m49,414s
user 0m50,742s
sys 0m10,332s
jas@kaka:~/src/oath-toolkit$
Thank you so much,
/Simon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2024-04-20 9:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 0:22 beta-tester call draft Bruno Haible
2024-04-20 0:39 ` Bruno Haible
2024-04-20 0:56 ` Collin Funk
2024-04-20 1:49 ` Bruno Haible
2024-04-20 4:27 ` Paul Eggert
2024-04-20 22:31 ` gnulib-tool: In sh+py mode, don't fail because of dangling symlinks Bruno Haible
2024-04-20 22:46 ` beta-tester call draft Bruno Haible
2024-04-20 9:38 ` Simon Josefsson via Gnulib discussion list [this message]
2024-04-20 22:50 ` gnulib-tool.py speedup Bruno Haible
2024-04-20 23:01 ` Collin Funk
2024-04-20 23:50 ` Bruno Haible
2024-04-21 0:53 ` Collin Funk
2024-04-20 10:21 ` beta-tester call draft Pádraig Brady
2024-04-20 13:05 ` Bernhard Voelker
2024-04-20 22:54 ` Bruno Haible
2024-04-20 22:57 ` Paul Eggert
2024-04-20 23:14 ` Bruno Haible
2024-04-21 10:53 ` Bernhard Voelker
2024-04-21 14:50 ` future Python evolution Bruno Haible
2024-04-21 15:14 ` Paul Eggert
2024-04-21 22:38 ` Bruno Haible
2024-04-22 7:05 ` Paul Eggert
2024-04-21 15:26 ` Bernhard Voelker
2024-04-28 14:14 ` Bernhard Voelker
2024-04-21 15:15 ` beta-tester call draft Janneke Nieuwenhuizen
2024-04-21 16:07 ` full-source bootstrap and Python Bruno Haible
2024-04-22 7:29 ` Simon Josefsson via Gnulib discussion list
2024-04-22 10:07 ` Bruno Haible
2024-04-22 10:06 ` Janneke Nieuwenhuizen
2024-04-22 11:24 ` Simon Josefsson via Gnulib discussion list
2024-04-22 15:48 ` 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=878r18fk6l.fsf@kaka.sjd.se \
--to=bug-gnulib@gnu.org \
--cc=bruno@clisp.org \
--cc=simon@josefsson.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).