From: ArsenArsen <ArsenArsen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: glibc: add INSTALL hook to make gconv module cache
Date: Sun, 28 Feb 2021 20:11:01 +0100 [thread overview]
Message-ID: <20210228191101.xk1Nk2-sVBYVMPFgPcqlOkPvgZoZbXu4LzO_3I7G_zw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29103@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
New comment by ArsenArsen on void-packages repository
https://github.com/void-linux/void-packages/pull/29103#issuecomment-787505300
Comment:
I've managed to test the changes on aarch64. The difference seems less significant, but it is consistent, and the cache is generated fine.
Before:
```
[arsen@void-live void-packages]$ time (for x in $(seq 1 100); do bash -c ''; done;)
real 0m6.681s
user 0m4.558s
sys 0m2.325s
[arsen@void-live void-packages]$ time (for x in $(seq 1 100); do python3 -c pass; done;)
real 0m47.313s
user 0m39.021s
sys 0m8.497s
[arsen@void-live void-packages]$
```
After:
```
[arsen@void-live void-packages]$ time (for x in $(seq 1 100); do bash -c ''; done;)
real 0m6.430s
user 0m4.570s
sys 0m2.091s
[arsen@void-live void-packages]$ time (for x in $(seq 1 100); do python3 -c pass; done;)
real 0m48.410s
user 0m40.391s
sys 0m8.228s
[arsen@void-live void-packages]$
```
next prev parent reply other threads:[~2021-02-28 19:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 21:57 [PR PATCH] " ArsenArsen
2021-02-27 21:58 ` [PR REVIEW] " ericonr
2021-02-27 22:12 ` [PR PATCH] [Updated] " ArsenArsen
2021-02-27 22:34 ` ArsenArsen
2021-02-27 22:36 ` ArsenArsen
2021-02-27 22:55 ` [PR REVIEW] " ericonr
2021-02-27 23:07 ` [PR PATCH] [Updated] " ArsenArsen
2021-02-28 7:10 ` ericonr
2021-02-28 19:11 ` ArsenArsen [this message]
2021-02-28 19:32 ` Duncaen
2021-02-28 20:44 ` ArsenArsen
2021-02-28 23:54 ` [PR PATCH] [Updated] " ArsenArsen
2021-03-02 7:07 ` [PR PATCH] [Updated] glibc: generate gconv cache when possible ArsenArsen
2021-03-04 18:02 ` ArsenArsen
2021-03-06 12:21 ` [PR PATCH] [Updated] " ArsenArsen
2021-08-24 18:11 ` [PR PATCH] [Updated] [NOMERGE] " ArsenArsen
2021-08-24 18:14 ` ArsenArsen
2022-05-05 2:09 ` github-actions
2022-05-19 2:15 ` [PR PATCH] [Closed]: " github-actions
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210228191101.xk1Nk2-sVBYVMPFgPcqlOkPvgZoZbXu4LzO_3I7G_zw@z \
--to=arsenarsen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).