[dart-misc] Source profiling is now available in Observatory

[John McCutchan]

Hi Dartisans,

You can now see which lines of code are hot, in any source view!

$ dart --observe DeltaBlue.dart

1. Navigate to a script view.

<Loading Image...>

2. Toggle profile display.

<Loading Image...>

Understanding the data:
- Profiler is sample driven so the performance data is an average.
- The column on the left is total time (including time spent waiting for
callees).
- The column on the right is executing time (does not include time spent
waiting for callees).
- Percentages are global to the whole program and not local to the function.

Known Issues:
- Not all generated code knows its source position, I will be improving
this.
- Some samples cannot be attributed directly to a line of code (register
spills, etc). These are accounted for internally but are not displayed in
the UI yet.

New issues:
- Please file bugs.

Thanks,
John

[John McCutchan]

I forgot to mention this will only be available in the next -dev release!

John

Post by John McCutchan
Hi Dartisans,
You can now see which lines of code are hot, in any source view!
$ dart --observe DeltaBlue.dart
1. Navigate to a script view.
<https://lh3.googleusercontent.com/-mevF2Gj6nR0/VugiKFeVsXI/AAAAAAAAQsE/_wwTNe5lxq4WZxWlCjAf84Vb3x390F0wg/s1600/ScriptView.png>
2. Toggle profile display.
<https://lh3.googleusercontent.com/-9W5wj0B5mMg/VugiPnL0jGI/AAAAAAAAQsI/jUgQpEKaf1Q0ifhYUuFFUzoBeJUesv4hQ/s1600/ProfileScriptView.png>
- Profiler is sample driven so the performance data is an average.
- The column on the left is total time (including time spent waiting for
callees).
- The column on the right is executing time (does not include time spent
waiting for callees).
- Percentages are global to the whole program and not local to the function.
- Not all generated code knows its source position, I will be improving
this.
- Some samples cannot be attributed directly to a line of code (register
spills, etc). These are accounted for internally but are not displayed in
the UI yet.
- Please file bugs.
Thanks,
John

[Günter Zöchbauer]

Great! This will increase test coverage a lot. Much more fun with proper
feedback :)

Post by John McCutchan
Hi Dartisans,
You can now see which lines of code are hot, in any source view!
$ dart --observe DeltaBlue.dart
1. Navigate to a script view.
<https://lh3.googleusercontent.com/-mevF2Gj6nR0/VugiKFeVsXI/AAAAAAAAQsE/_wwTNe5lxq4WZxWlCjAf84Vb3x390F0wg/s1600/ScriptView.png>
2. Toggle profile display.
<https://lh3.googleusercontent.com/-9W5wj0B5mMg/VugiPnL0jGI/AAAAAAAAQsI/jUgQpEKaf1Q0ifhYUuFFUzoBeJUesv4hQ/s1600/ProfileScriptView.png>
- Profiler is sample driven so the performance data is an average.
- The column on the left is total time (including time spent waiting for
callees).
- The column on the right is executing time (does not include time spent
waiting for callees).
- Percentages are global to the whole program and not local to the function.
- Not all generated code knows its source position, I will be improving
this.
- Some samples cannot be attributed directly to a line of code (register
spills, etc). These are accounted for internally but are not displayed in
the UI yet.
- Please file bugs.
Thanks,
John

[Jim Trainor]

This is awesome. Thanks.

Presumably this will profiling information will be available from
observatory?

Post by Günter Zöchbauer
Great! This will increase test coverage a lot. Much more fun with proper
feedback :)

Post by John McCutchan
Hi Dartisans,
You can now see which lines of code are hot, in any source view!
$ dart --observe DeltaBlue.dart
1. Navigate to a script view.
<https://lh3.googleusercontent.com/-mevF2Gj6nR0/VugiKFeVsXI/AAAAAAAAQsE/_wwTNe5lxq4WZxWlCjAf84Vb3x390F0wg/s1600/ScriptView.png>
2. Toggle profile display.
<https://lh3.googleusercontent.com/-9W5wj0B5mMg/VugiPnL0jGI/AAAAAAAAQsI/jUgQpEKaf1Q0ifhYUuFFUzoBeJUesv4hQ/s1600/ProfileScriptView.png>
- Profiler is sample driven so the performance data is an average.
- The column on the left is total time (including time spent waiting for
callees).
- The column on the right is executing time (does not include time spent
waiting for callees).
- Percentages are global to the whole program and not local to the function.
- Not all generated code knows its source position, I will be improving
this.
- Some samples cannot be attributed directly to a line of code (register
spills, etc). These are accounted for internally but are not displayed in
the UI yet.
- Please file bugs.
Thanks,
John

--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
---
You received this message because you are subscribed to the Google Groups
"Dart Misc" group.
To unsubscribe from this group and stop receiving emails from it, send an