From: Mark Geisert <mark@maxrnd.com>
To: cygwin-developers@cygwin.com
Subject: Re: Maybe consider rpmalloc
Date: Tue, 13 Apr 2021 01:24:45 -0700 [thread overview]
Message-ID: <69159cfa-8fc5-283b-126b-740b841841cd@maxrnd.com> (raw)
In-Reply-To: <CAEHcbmdsQBFzCHD_zgyADQ-7+1De0O0JMz0Gp=vhfP_XFsKarg@mail.gmail.com>
Hi Teemu,
Teemu Nätkinniemi wrote:
> Hello,
>
> Thanks for testing! I found a better test case with smaller files
> which should clearly show the issue.
>
> https://drive.google.com/drive/folders/1jOilHtKrr6CHn7zg__DE93RCDyseoTB1?usp=sharing
>
> Here's the results. Bwa_working is the one with rpmalloc and
> bwa_original is unpatched. As you can see the unpatched version with
> several threads takes a whole lot more time to finish even when
> compared with unpatched exe running with a single thread. I am not the
> only one experiencing the issue so I doubt it is my system.
[...]
Well this certainly does show the issue(s) you're seeing. Short runs but long
enough for me to get decent profiling. Yes, malloc code shows up a lot in the
profiles.
I'm going to research some stuff and ask some questions of the Cygwin gurus to see
if we can do something about this.
Thanks a bunch,
..mark
next prev parent reply other threads:[~2021-04-13 8:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 6:01 Cygwin malloc tune-up status Mark Geisert
2020-09-27 16:54 ` Johannes Schindelin
2020-09-29 2:22 ` Mark Geisert
2021-04-01 9:19 ` Teemu Nätkinniemi
2021-04-02 5:45 ` Maybe consider rpmalloc -- Was: " Mark Geisert
2021-04-03 2:53 ` Maybe consider rpmalloc Mark Geisert
2021-04-03 6:46 ` Teemu Nätkinniemi
2021-04-03 6:48 ` Teemu Nätkinniemi
2021-04-11 9:28 ` Mark Geisert
2021-04-12 8:48 ` Teemu Nätkinniemi
2021-04-13 8:24 ` Mark Geisert [this message]
2021-04-13 13:05 ` Teemu Nätkinniemi
2021-04-14 8:19 ` Mark Geisert
2021-04-14 18:36 ` Teemu Nätkinniemi
2021-04-14 18:53 ` Jon Turney
2021-04-19 5:16 ` Mark Geisert
2021-04-20 19:34 ` Jon Turney
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=69159cfa-8fc5-283b-126b-740b841841cd@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin-developers@cygwin.com \
/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).