See this profile from a capture of loading https://www.mozilla.org: https://deploy-preview-1917--perf-html.netlify.com/public/b2a52d4f27616a7baf9fae7449edadb76ff01e88/network-chart/?globalTrackOrder=0-1-2-3-4-5-6-7-8&hiddenGlobalTracks=1-2-3-4-5-6-8&localTrackOrderByPid=3164-1-2-0~12671-0~12605-0~12886-0~12803-0~12665-0~13172-0~13100-0-1~12558-0-1~&thread=8&v=3 There are 3 markers showing up for the loading phase of the HTML page: 1. The initial load. { "start": 512335.72875789064, "dur": 3056.424849999952, "name": "Load 36: https://www.mozilla.org/", "title": null, "data": { "type": "Network", "startTime": 512335.72875789064, "endTime": 512337.07070589066, "id": 56264071577636, "status": "STATUS_START", "pri": 0, "URI": "https://www.mozilla.org/" }, "incomplete": true } 2. The answer with the redirection { "start": 505780.25126389065, "dur": 6618.132344999933, "name": "Load 1884: https://www.mozilla.org/", "title": null, "data": { "type": "Network", "startTime": 505780.25126389065, "endTime": 512398.3836088906, "id": 13589276526428, "status": "STATUS_REDIRECT", "pri": -20, "URI": "https://www.mozilla.org/", "RedirectURI": "https://www.mozilla.org/en-US/", "fetchStart": 512337.07070589066 }, "incomplete": true } 3. The final answer. { "start": 505780.25126389065, "dur": 6700.485168999992, "name": "Load 1884: https://www.mozilla.org/en-US/", "title": null, "data": { "type": "Network", "startTime": 505780.25126389065, "endTime": 512480.73643289064, "id": 13589276526428, "status": "STATUS_STOP", "pri": -20, "URI": "https://www.mozilla.org/en-US/", "fetchStart": 512398.60101289063 }, "incomplete": true } In the current process, we don't match these 3 markers. We see that 2 and 3 share their ids, so we should match them, and probably handle the marker 2 as the START for the marker 3. (I'll just do it in a coming patch). But we don't have any way to match 1 and 2: their ids are different, and their names are different. I believe this is an important issue as this prevents us from showing the right data to the user.
Bug 1546641 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
See this profile from a capture of loading https://www.mozilla.org: https://deploy-preview-1917--perf-html.netlify.com/public/b2a52d4f27616a7baf9fae7449edadb76ff01e88/network-chart/?globalTrackOrder=0-1-2-3-4-5-6-7-8&hiddenGlobalTracks=1-2-3-4-5-6-8&localTrackOrderByPid=3164-1-2-0~12671-0~12605-0~12886-0~12803-0~12665-0~13172-0~13100-0-1~12558-0-1~&thread=8&v=3 There are 3 markers showing up for the loading phase of the HTML page: 1. The initial load. ```json { "start": 512335.72875789064, "dur": 3056.424849999952, "name": "Load 36: https://www.mozilla.org/", "title": null, "data": { "type": "Network", "startTime": 512335.72875789064, "endTime": 512337.07070589066, "id": 56264071577636, "status": "STATUS_START", "pri": 0, "URI": "https://www.mozilla.org/" }, "incomplete": true } ``` 2. The answer with the redirection ```json { "start": 505780.25126389065, "dur": 6618.132344999933, "name": "Load 1884: https://www.mozilla.org/", "title": null, "data": { "type": "Network", "startTime": 505780.25126389065, "endTime": 512398.3836088906, "id": 13589276526428, "status": "STATUS_REDIRECT", "pri": -20, "URI": "https://www.mozilla.org/", "RedirectURI": "https://www.mozilla.org/en-US/", "fetchStart": 512337.07070589066 }, "incomplete": true } ``` 3. The final answer. ```json { "start": 505780.25126389065, "dur": 6700.485168999992, "name": "Load 1884: https://www.mozilla.org/en-US/", "title": null, "data": { "type": "Network", "startTime": 505780.25126389065, "endTime": 512480.73643289064, "id": 13589276526428, "status": "STATUS_STOP", "pri": -20, "URI": "https://www.mozilla.org/en-US/", "fetchStart": 512398.60101289063 }, "incomplete": true } ``` In the current process, we don't match these 3 markers. We see that 2 and 3 share their ids, so we should match them, and probably handle the marker 2 as the START for the marker 3. (I'll just do it in a coming patch). But we don't have any way to match 1 and 2: their ids are different, and their names are different. I believe this is an important issue as this prevents us from showing the right data to the user.
See this profile from a capture of loading https://www.mozilla.org: https://deploy-preview-1917--perf-html.netlify.com/public/b2a52d4f27616a7baf9fae7449edadb76ff01e88/network-chart/?globalTrackOrder=0-1-2-3-4-5-6-7-8&hiddenGlobalTracks=1-2-3-4-5-6-8&localTrackOrderByPid=3164-1-2-0~12671-0~12605-0~12886-0~12803-0~12665-0~13172-0~13100-0-1~12558-0-1~&thread=8&v=3 There are 3 markers showing up for the loading phase of the HTML page: 1. The initial load. ```json { "start": 512335.72875789064, "dur": 3056.424849999952, "name": "Load 36: https://www.mozilla.org/", "title": null, "data": { "type": "Network", "startTime": 512335.72875789064, "endTime": 512337.07070589066, "id": 56264071577636, "status": "STATUS_START", "pri": 0, "URI": "https://www.mozilla.org/" }, "incomplete": true } ``` 2. The answer with the redirection ```json { "start": 505780.25126389065, "dur": 6618.132344999933, "name": "Load 1884: https://www.mozilla.org/", "title": null, "data": { "type": "Network", "startTime": 505780.25126389065, "endTime": 512398.3836088906, "id": 13589276526428, "status": "STATUS_REDIRECT", "pri": -20, "URI": "https://www.mozilla.org/", "RedirectURI": "https://www.mozilla.org/en-US/", "fetchStart": 512337.07070589066 }, "incomplete": true } ``` 3. The final answer. ```json { "start": 505780.25126389065, "dur": 6700.485168999992, "name": "Load 1884: https://www.mozilla.org/en-US/", "title": null, "data": { "type": "Network", "startTime": 505780.25126389065, "endTime": 512480.73643289064, "id": 13589276526428, "status": "STATUS_STOP", "pri": -20, "URI": "https://www.mozilla.org/en-US/", "fetchStart": 512398.60101289063 }, "incomplete": true } ``` In the current process, we don't match these 3 markers. We see that 2 and 3 share their ids, so we should match them, and probably handle the marker 2 as the START for the marker 3. (I'll just do it in a coming patch). But we don't have any way to match 1 and 2: their ids are different, and their names are different. I believe this is an important issue as this prevents us from showing the right data to the user.