Github messages for voidlinux
 help / color / mirror / Atom feed
From: wangp <wangp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: mimalloc-2.0.6, mold-1.4.2
Date: Thu, 22 Sep 2022 02:57:12 +0200	[thread overview]
Message-ID: <20220922005712.PrtESopiX-JfIBxftc1U5M994kZxUrxjvoVSv6JbnCE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37688@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

New comment by wangp on void-packages repository

https://github.com/void-linux/void-packages/pull/37688#issuecomment-1254376906

Comment:
Interesting suggestion. I will add the build option, but I would like other people's opinions if it should be the default.

I'm mainly packaging mimalloc to use with mold. Here is a benchmark of mold on my machine.
Benchmark # 1 uses mold with mimalloc in non-secure mode.
Benchmark # 2 uses mold with mimalloc in secure mode.
```
Benchmark #1: ../../link-test.sh
  Time (mean ± σ):     255.3 ms ±   1.5 ms    [User: 22.2 ms, System: 7.4 ms]
  Range (min … max):   252.9 ms … 257.7 ms    20 runs
 
Benchmark #2: LD_LIBRARY_PATH=/tmp/mimalloc-secure/usr/lib ../../link-test.sh
  Time (mean ± σ):     265.1 ms ±   1.7 ms    [User: 26.8 ms, System: 8.1 ms]
  Range (min … max):   261.7 ms … 267.6 ms    20 runs
 
Summary
  '../../link-test.sh' ran
    1.04 ± 0.01 times faster than 'LD_LIBRARY_PATH=/tmp/mimalloc-secure/usr/lib ../../link-test.sh', -3.7%
```
In relative terms, a 3-4% slowdown is significant, but in absolute terms, 10 ms is not something that I would notice. So I think I would be okay with making secure mode the default, even if I don't see the need for it in a linker.

(For interest, the same link command using GNU ld takes 1.9 s.)

  parent reply	other threads:[~2022-09-22  0:57 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-26  4:26 [PR PATCH] New package: mimalloc-2.0.6 wangp
2022-06-26  5:06 ` [PR PATCH] [Updated] " wangp
2022-09-11  2:48 ` wangp
2022-09-11  5:01 ` New packages: mimalloc-2.0.6, mold-1.4.2 wangp
2022-09-16 15:30 ` icp1994
2022-09-16 16:38 ` icp1994
2022-09-17  4:28 ` [PR PATCH] [Updated] " wangp
2022-09-17  4:29 ` wangp
2022-09-17  4:40 ` wangp
2022-09-18  2:21 ` [PR PATCH] [Updated] " wangp
2022-09-18  2:22 ` wangp
2022-09-18  8:45 ` [PR PATCH] [Updated] " wangp
2022-09-19 16:18 ` [PR REVIEW] " cinerea0
2022-09-19 16:18 ` cinerea0
2022-09-22  0:57 ` wangp [this message]
2022-10-01  1:31 ` [PR PATCH] [Updated] " wangp
2022-10-01  1:33 ` wangp
2022-10-01  2:41 ` [PR PATCH] [Updated] New packages: mimalloc-2.0.6, mold-1.5.1 wangp
2022-10-01  7:33 ` wangp
2022-10-01  7:33 ` wangp
2022-10-22  1:50 ` wangp
2022-10-23  1:41 ` wangp
2022-10-23  2:21 ` wangp
2022-10-24 14:24 ` New packages: mimalloc-2.0.6, mold-1.6.0 sug0
2022-12-02  7:23 ` [PR PATCH] [Updated] " wangp
2023-01-08  0:42 ` [PR PATCH] [Updated] New packages: mimalloc-2.0.7, mold-1.7.1 wangp
2023-01-08  5:58 ` New packages: mimalloc-2.0.9, mold-1.9.0 icp1994
2023-01-08 17:54 ` [PR REVIEW] " classabbyamp
2023-01-09  1:00 ` nekopsykose
2023-01-09  4:54 ` nekopsykose
2023-01-21  5:01 ` [PR PATCH] [Updated] " wangp
2023-03-02 22:22 ` subnut
2023-03-02 23:02 ` [PR REVIEW] " subnut
2023-03-02 23:05 ` subnut
2023-03-04  0:55 ` [PR PATCH] [Updated] " wangp
2023-03-04  0:57 ` [PR REVIEW] " wangp
2023-03-27 18:37 ` New packages: mimalloc-2.0.9, mold-1.10.1 cinerea0
2023-04-02  1:04 ` [PR PATCH] [Updated] " wangp
2023-06-20  7:36 ` [PR PATCH] [Updated] New packages: mimalloc-2.0.9, mold-1.11.0 wangp
2023-07-27 16:01 ` New packages: mimalloc-2.1.2, mold-1.11.0 sug0
2023-07-29 14:30 ` leahneukirchen
2023-07-31  8:51 ` [PR PATCH] [Updated] " wangp
2023-07-31 15:29 ` [PR PATCH] [Merged]: " leahneukirchen

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=20220922005712.PrtESopiX-JfIBxftc1U5M994kZxUrxjvoVSv6JbnCE@z \
    --to=wangp@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).