Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>,
	Pedro Alves <pedro@palves.net>
Subject: Re: [PATCH][gdbsupport] Use task size in parallel_for_each
Date: Sun, 31 Jul 2022 10:38:33 +0200	[thread overview]
Message-ID: <07a7deb5-e33e-9c0a-ec34-02d81c0364d6@suse.de> (raw)
In-Reply-To: <f79bb763-aec8-4fa4-f063-ac119f85764f@suse.de>

On 7/23/22 08:51, Tom de Vries via Gdb-patches wrote:
> On 7/22/22 23:21, Tom Tromey wrote:
>> Tom> Then, rather than using parallel_for, the DWARF reader could send 
>> N jobs
>> Tom> to the thread pool, and each job would simply take the next 
>> available CU
>> Tom> by incrementing an atomic counter.  When the counter reached the 
>> number
>> Tom> of CUs, a job would stop.
>>
>> Here's a patch.  I didn't test it much, though according to "maint 
>> time 1",
>> it is ~10% faster on gdb itself.  I pushed it as "t/work-stealing" on my
>> github as well, in case you want to try it out.
>>
> 
> I've tried it out (initially didn't build for me with gcc 7.5.0, but it 
> did after using gcc 12.1.1).
> 
> So, the same libxul experiment as before, gcc-12, O2, base commit 
> 5ae3df226b1.
> 
> ---
> 
> base commit:
> 
> real: 4.64
> real: 4.10
> real: 4.11
> real: 4.65
> real: 4.04
> real: 4.21
> real: 4.03
> real: 4.48
> real: 4.04
> real: 4.65
> 
> t/work-stealing:
> 
> real: 3.65
> real: 3.58
> real: 3.58
> real: 3.58
> real: 3.58
> real: 3.57
> real: 3.58
> real: 3.59
> real: 3.59
> real: 3.59
> 
> size heuristics:
> 
> real: 3.44
> real: 3.44
> real: 3.52
> real: 3.43
> real: 3.54
> real: 3.47
> real: 3.60
> real: 3.46
> real: 3.46
> real: 3.52
> 
> Just one data point of course.
> 

I've rebase the patch series on the latest version for the 
gdb::make_function_view patch, and retested using the try-bot.  If there 
are no further comments, I'll commit in a week or so.

Thanks,
- Tom

  reply	other threads:[~2022-07-31  8:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 19:42 Tom de Vries via Gdb-patches
2022-07-21 17:35 ` Pedro Alves
2022-07-21 20:23   ` Tom de Vries via Gdb-patches
2022-07-22  0:03     ` Pedro Alves
2022-07-22 11:07       ` Pedro Alves
2022-07-22 17:07       ` Tom de Vries via Gdb-patches
2022-07-22 19:08     ` Tom Tromey
2022-07-22 19:38       ` Simon Marchi via Gdb-patches
2022-07-23  3:17         ` Tom Tromey
2022-07-22 21:21       ` Tom Tromey
2022-07-23  6:51         ` Tom de Vries via Gdb-patches
2022-07-31  8:38           ` Tom de Vries via Gdb-patches [this message]
2022-07-23  5:55       ` Tom de Vries via Gdb-patches

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=07a7deb5-e33e-9c0a-ec34-02d81c0364d6@suse.de \
    --to=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.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