public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Wei-min Pan <weimin.pan@oracle.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb.base/siginfo-thread.exp: Increase timeout for 'gcore' command
Date: Thu, 16 Mar 2017 19:51:00 -0000	[thread overview]
Message-ID: <58CAECA1.10707@oracle.com> (raw)
In-Reply-To: <19e4cf44-5e49-09ef-4055-14b611fc64c2@redhat.com>

Pedro Alves wrote:
> On 03/16/2017 07:10 PM, Wei-min Pan wrote:
>
>   
>>> You mean that by hand it went faster than that?
>>> So what is GDB doing differently when run via make check
>>> that makes it slower than running by hand?
>>>   
>>>       
>> Yes, but not by much faster:
>>
>> % cat in
>> run
>> gcore tmp.gcore
>> quit
>>
>> % time my_gdb siginfo-thread -x in
>> ...
>> real    0m13.327s
>> user    0m3.504s
>> sys     0m7.572s
>>     
>
> Either I'm missing something, or that was _slower_ than then
> number you shown of running via the testsuite, not faster...
>   

Sorry, you didn't miss anything. I misspoke :)
> So WDT is GDB doing that takes that long?  Is that writing
> the core to a slow NFS mount or something?
>
> Here that takes:
>
>  real    0m0.120s
>  user    0m0.090s
>  sys     0m0.033s
>
> and this is not a state-of-the-art machine.
>
> Can you guess the next question?
>
> Pick any other core test in the testsuite, do the
> same and compare the numbers.
>
> And if they're different, the next question would
> then be, "what's different in this test, why's
> it slower?".
>   
OK, just tried a different test which is similar to siginfo-thread:

% time make check TESTS="*/siginfo-obj.exp"
...
real    0m1.282s
user    0m0.736s
sys     0m0.400s

Looks like the slowness had something to do with the pthread libs.
Will investigate. Thanks.
> If they're similar, then, well, the same question.  :-)
>
> Thanks,
> Pedro Alves
>
>   

      reply	other threads:[~2017-03-16 19:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01  3:23 Weimin Pan
2017-03-16 14:45 ` Yao Qi
2017-03-16 16:00   ` Wei-min Pan
2017-03-16 17:08     ` Pedro Alves
2017-03-16 18:27       ` Wei-min Pan
2017-03-16 18:34         ` Pedro Alves
2017-03-16 19:10           ` Wei-min Pan
2017-03-16 19:21             ` Pedro Alves
2017-03-16 19:51               ` Wei-min Pan [this message]

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=58CAECA1.10707@oracle.com \
    --to=weimin.pan@oracle.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=qiyaoltc@gmail.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).