New issue
Advanced search Search tips

Issue 602938 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Understand the cost of first/third party content from tracing result

Project Member Reported by xiaoche...@chromium.org, Apr 13 2016

Issue description

This is a tracing bug for the implementation of understanding the cost of first/third party content from tracing result. Currently there is no clear way to do so in default chrome.
 
A rough roadmap:

1. In tracing, add frame info to as many necessary slices as possible

2. Given tracing with frame info, design a model for attributing cost to first and third party frames

3. Implement the model in Catapult
Status: WontFix (was: Assigned)

Sign in to add a comment