core(insights): implement network-dependency-tree insight
#16407
Conversation
| }; | ||
|
|
||
| interface NetworkTree extends BaseDetails { | ||
| type: 'network-tree'; |
There was a problem hiding this comment.
This new detail type is introduced to address the differences in how the network tree is displayed in RPP vs the old CRC audit:
- The CRC audit will show individual request durations but the new NDT insight will show the entire chain duration
- The CRC audit will only show any timing/transfer size info for leaf node requests, but the NDT insight will show this info for all requests
- The CRC audit contains extra request timing info like
responseReceivedTimebut we don't need this for the NDT insight. The NDT insight has enough information to fill in this extra data, but I don't want to add extra calculations just to fill in the CRC detail type.
See report/renderer/crc-details-renderer.js for more info on how these detail types are handled.
There was a problem hiding this comment.
The CRC audit contains extra request timing info like responseReceivedTime but we don't need this for the NDT insight. The NDT insight has enough information to fill in this extra data, but I don't want to add extra calculations just to fill in the CRC detail type.
can we stuff that info into a title tooltip?
| /** | ||
| * Recursively builds a tree from segments. | ||
| * @param {DOM} dom | ||
| * @param {DocumentFragment} tmpl |
There was a problem hiding this comment.
tmpl and details are never actually used anywhere, they just get passed through the recursive calls.
| * @property {boolean} isLastChild | ||
| * @property {boolean} hasChildren | ||
| * @property {number} startTime | ||
| * @property {number} transferSize |
There was a problem hiding this comment.
startTime and transferSize are never actually used anywhere. Instead, createChainNode will just look at the data in node.
adamraine
changed the title
network-dependency-tree insightnetwork-dependency-tree insight
|
could we un-bold the byte portion of each row? it's the timing that is more important |
|
in the insight card we highlight (subtly...) the actual critical path: 
and if you hover (this works for any node): 
note how the "max latency" label color matches each part of the longest critical path. can we do the same in LH? |
|
Yeah, it was a pretty simple change: |
3 participants
Ref #16323
This introduces a new audit detail type
network-treewhich will eventually replace thecriticalrequestchain. They use most of the same rendering code on the report side, but there are some key differences that made a separate detail type compelling: #16407 (comment)