Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: John Harrison <John.C.Harrison@Intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] scripts/trace.pl: Optimize event parsing and processing
Date: Thu, 21 Dec 2017 09:34:13 +0000	[thread overview]
Message-ID: <4fd3b62b-ce5d-d05b-ce07-adf88d4ae838@linux.intel.com> (raw)
In-Reply-To: <0b473f69-efd0-52ab-8ba6-799470142a0b@Intel.com>


On 20/12/2017 23:50, John Harrison wrote:
> On 12/20/2017 1:54 AM, Tvrtko Ursulin wrote:
>> What was the effect of all this on your big traces? I am only testing 
>> with a smaller one which goes from ~3.3s to ~2.2s. On a larger trace 
>> it might be non-linear gains due to double sort avoidance, unless 
>> there will be some other effects to cancel that out.
>>
> 
> So with a trace of a shortened gem_exec_nop/basic_sequential, the 'perf 
> script' output is 439MB and the original trace.pl before any of the 
> changes took ~180s. After the 'auto-detect field order' patch, it went 
> up to ~201s. With the optimisation patch it is down to ~129s.
> 
> However, I am also seeing differences in the HTML output since the 
> optimisation patch. The differences aren't massive, just slight 
> variations in the times. The structure is all the same, its just that 
> the accounting and/or time stamps are out.
> 
> For example:
>      {id: 1, content: 'Ring0<br><small><br>79.48% idle<br><br>34.32% 
> busy<br>584.97% runnable<br>2103.60% queued<br><br>16.18% 
> wait<br><br>200931 batches<br>331.28us avg batch<br>331.38us avg engine 
> batch<br></small>'},
> vs
>      {id: 1, content: 'Ring0<br><small><br>79.48% idle<br><br>34.32% 
> busy<br>584.97% runnable<br>2103.60% queued<br><br>16.18% 
> wait<br><br>200931 batches<br>338.56us avg batch<br>338.56us avg engine 
> batch<br></small>'},
> 
> Or:
>      {id: 58, key: -210383407,  type: 'range', group: 4, subgroup: 2, 
> subgroupOrder: 3, content: '428/3 <small>0</small> 
> <small><i>???</i></small> <small><i>++</i></small> <br>142us 
> <small>(0us)</small>', start: '2017-01-05 21:27:45.352968', end: 
> '2017-01-05 21:27:45.353110', style: 'color: white; background-color: 
> red;'},
> vs
>      {id: 58, key: -210383407,  type: 'range', group: 4, subgroup: 2, 
> subgroupOrder: 3, content: '428/3 <small>0</small> 
> <small><i>???</i></small> <small><i>++</i></small> <br>159us 
> <small>(0us)</small>', start: '2017-01-05 21:27:45.352968', end: 
> '2017-01-05 21:27:45.353127', style: 'color: white; background-color: 
> red;'},
> 
> I can send you the full output if it is useful and the source logs too. 
> The HTML output is about 840KB but as noted, the perf logs are hundreds 
> of MBs.

I was able to reproduce it. I think it's down to floating point 
mishandling. Neither the original nor the optimized version were correct 
and both are accumulating error. I'll send an updated patch shortly.

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-12-21  9:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 11:15 [PATCH i-g-t] scripts/trace.pl: Optimize event parsing and processing Tvrtko Ursulin
2017-12-19 11:39 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-12-19 13:23 ` ✓ Fi.CI.IGT: " Patchwork
2017-12-19 15:02 ` [PATCH i-g-t] " Chris Wilson
2017-12-19 16:23 ` John Harrison
2017-12-20  9:41   ` [PATCH i-g-t v2] " Tvrtko Ursulin
2017-12-21  9:37     ` [PATCH i-g-t v3] " Tvrtko Ursulin
2017-12-20  9:54   ` [PATCH i-g-t] " Tvrtko Ursulin
2017-12-20 23:50     ` John Harrison
2017-12-21  9:34       ` Tvrtko Ursulin [this message]
2017-12-21 22:44         ` John Harrison
2017-12-22  9:16           ` [PATCH i-g-t v4] " Tvrtko Ursulin
2017-12-22 20:38             ` John Harrison
2017-12-20 10:33 ` ✗ Fi.CI.BAT: failure for scripts/trace.pl: Optimize event parsing and processing (rev2) Patchwork
2017-12-21 11:11 ` ✓ Fi.CI.BAT: success for scripts/trace.pl: Optimize event parsing and processing (rev3) Patchwork
2017-12-21 13:27 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-12-22  9:34 ` ✓ Fi.CI.BAT: success for scripts/trace.pl: Optimize event parsing and processing (rev5) Patchwork
2017-12-22 10:21 ` ✓ Fi.CI.IGT: " Patchwork

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=4fd3b62b-ce5d-d05b-ce07-adf88d4ae838@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=John.C.Harrison@Intel.com \
    --cc=tursulin@ursulin.net \
    /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