Update Blazorwasm PowerBi

[ooooolivia]

This issue is for gathering feedbacks and tracking to-do items for Blazorwasm PowerBi dashboard. Feel free to comment below to suggest other improvements on the dashboard.

• validation for automatic data refresh
• trim part of the path to fit in the graph (not able to due to aggregation problem, but 'file name' added in the tooltip )
• add link to linker dump
• link graphs and remove the build time filters (abandoned due to power bi limit)
• make trend graphs not dynamic based for easier detection of anomalies/noise
• clarify master branch
• add preview 8 branch
• individual graph for each binary
• select latest build in treemap (abandoned due to power bi limit)
• show installer version
• fill in missing data between 7/12 - 7/17
• update baseline to include .br files
  ------------------------- from 8/3/2020 sync-up --------------------------------
• add commit hash next to build time list
• add support for dynamic start & end points of graph range
• add a drop-down menu for the list of files
• extend preview branches as static baseline
• mark unit of the axis (crossgen report)

[danmoseley]

does it make sense to have separate "square diagrams" for uncompressed, gzip and brotli? the size of the whole is not significant - we care about them separately. I don't feel strongly either way

[ooooolivia]

@danmosemsft If you scroll down to the second page in the dashboard, you can choose to only show treemap of a particular file type by selecting the "File Type" filter on the right, if that's equivalent to "have separate square diagrams".

[danmoseley]

Ah - thanks

[marek-safar]

I disagree with enhancement classification. The dashboard as-is today does not work at all. The last update is from 3 weeks ago and data included as pointed our by @eerhardt are wrong (3.2 data used for master). Please work on fixing the fundamentals problems first.

[ooooolivia]

@marek-safar Since when did blazorwasm transition from 3.2 to 5.0? We do notice that in preview 6 there's still 3.2 template, and that's what our data reflect. We are actively fixing the data transfer pipeline for blazor since it's just set up.

[marek-safar]

Since when did blazorwasm transition from 3.2 to 5.0

It was in .NET5 P7 but I'm not sure if that matters. We need to be able to track master changes at least daily (ideally even more than that).

[ooooolivia]

@marek-safar by "master" do you mean blazor master? If SDK master still carries blazor3.2 version as it's unsynced, we are happy to remove the data that still shows blazor3.2 but from SDK 5.0. In our graph, the "master" means the installer's master branch.

[marek-safar]

by "master" do you mean blazor master?

Yes.

[ooooolivia]

There's an issue in the installer repo that the latest asset produced stays at 7/12/2020 dotnet/installer#8011 and dotnet/installer#8012 , will keep tracking this issue.

[lewing]

The data and graphs are getting much better day by day, thank you so much for working on this. One thing that is consistently confusing is the lack of 0 lower bound, would it be possible to include a small lower bound to force power bi to scale graphs in absolute terms?

[ooooolivia]

@lewing Thanks for the feedback! Yes the trend graph has just been updated with fixed start and end values. Changes in smaller files may be too trivial to identify now. Please let me know if you'd prefer separate graphs for large values and small values.