From: Yichao Yu <yyc1992@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb@sourceware.org, Paul Pluzhnikov <ppluzhnikov@google.com>
Subject: Re: JIT debugging (Attach and speed)
Date: Thu, 24 Mar 2016 21:02:00 -0000 [thread overview]
Message-ID: <CAMvDr+QGf+WHgqkkn8Nn8HJ5XqXSMFG60__XZE5=D9Fxs_PE4Q@mail.gmail.com> (raw)
In-Reply-To: <CAMvDr+S4pwdPwdRK71uwTqcCc5CoNHHsUuZQKAqbF4JG+y3Evg@mail.gmail.com>
> There's indeed a huge improvement. The test I was using with ~2000 JIT
> objects goes drops from ~400s to 7.5s (~3s without gdb). However a
> rough scaling test suggests that the scaling is still ~O(n^2) 20k JIT
> objects takes ~500s (~130s without gdb). It seems that the master was
> actually super quadratic (if this is a word) when dealing with
> multiple JIT objects.
The new profile is [1] and it is indeed much closer to the one in 2011.
[1] http://i.imgur.com/K3GKYeq.jpg
>
>> Having a pending breakpoint that is never resolved slows things down
>> significantly again though... The perf profile shows that breakpoint_re_set
>> ends up calling parse_linespec which wants the selected block, which wants
>> the selected frame, and then we're back at the same... Maybe we
>> could reconsider how pending breakpoints are re-parsed, and which
>> context they're parsed in. Not sure.
>>
>> Still, very promising.
>>
>
> Indeed. It's already so much better.
next prev parent reply other threads:[~2016-03-24 21:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 14:56 Yichao Yu
2016-03-22 15:46 ` Pedro Alves
2016-03-22 16:10 ` Paul Pluzhnikov
2016-03-22 16:15 ` Pedro Alves
2016-03-22 16:23 ` Yichao Yu
2016-03-22 16:41 ` Pedro Alves
2016-03-22 16:47 ` Yichao Yu
2016-03-22 17:00 ` Pedro Alves
2016-03-23 2:18 ` Yichao Yu
2016-03-23 4:51 ` Yichao Yu
2016-03-23 18:24 ` Pedro Alves
2016-03-23 19:32 ` Yichao Yu
2016-03-23 19:48 ` Pedro Alves
2016-03-23 20:51 ` Yichao Yu
2016-03-24 1:17 ` Pedro Alves
2016-03-24 3:14 ` Yichao Yu
2016-03-24 21:02 ` Yichao Yu [this message]
2016-03-23 12:24 ` Pedro Alves
2016-03-23 13:31 ` Pedro Alves
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='CAMvDr+QGf+WHgqkkn8Nn8HJ5XqXSMFG60__XZE5=D9Fxs_PE4Q@mail.gmail.com' \
--to=yyc1992@gmail.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=ppluzhnikov@google.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