Chrome `.cpuprofile` importer: Get profile start time from URL (Chrome DevTools UI format) #4797

kazarmy · 2023-11-11T08:50:00Z

This PR obtains a Chrome .cpuprofile start time from its URL / filename. The timestamp format currently supported is what is generated by the Chrome DevTools UI when one manually saves a profile from the Performance tab. The format, and the claim that the timestamp is generated on profile save, is based on https://chromium.googlesource.com/chromium/blink/+/refs/heads/main/Source/devtools/front_end/profiler/CPUProfileView.js#727.

Change will manifest itself as an accurate timestamp here:

Questions:

Currently, the URL is from window.location.href. Should profileUrl be passed to unserializeProfileOfArbitraryFormat() instead?
Add test (that has profile with timestamp in filename)?

(As a side note, the profile given to the Profiler.consoleProfileFinished event handler is slightly different from the profile generated when it is saved manually through the UI. No idea why.)

┆Issue is synchronized with this Jira Task

…e DevTools UI format)

codecov · 2023-11-11T09:15:18Z

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.62%. Comparing base (532edf0) to head (b262540).
Report is 32 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4797   +/-   ##
=======================================
  Coverage   88.62%   88.62%           
=======================================
  Files         308      308           
  Lines       28051    28059    +8     
  Branches     7596     7598    +2     
=======================================
+ Hits        24859    24867    +8     
  Misses       2978     2978           
  Partials      214      214

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles

kazarmy · 2023-11-11T10:02:51Z

Add test (that has profile with timestamp in filename)?

I guess Codecov has answered this question.

…nto chrome-profile-start-time

kazarmy · 2023-11-20T15:27:50Z

Currently, the URL is from window.location.href. Should profileUrl be passed to unserializeProfileOfArbitraryFormat() instead?

The profile conversion tests don't run a (headless) browser and so window.location.href isn't available in the tests and I had no choice but to pass profileUrl to unserializeProfileOfArbitraryFormat().

The test profile is actually an old profile produced using node --cpu-prof that I loaded and resaved in Node DevTools. Sorry for the lack of movement on this, current geopolitical situation not helping.

…d test

…nto chrome-profile-start-time

julienw · 2023-11-23T18:18:54Z

Just checking: I see you were doing some changes recently, so can you please precise if it's ready for review now? Thanks :-)

…nto chrome-profile-start-time

kazarmy · 2023-11-24T01:07:35Z

... so can you please precise if it's ready for review now?

Yes, it's ready for review.

…nto chrome-profile-start-time

julienw

Thanks for your patience, while we were busy with other work.

I believe it is reasonable to pass "something" to the unserializing function.

We also need to pass the file name from retrieveProfileFromFile in the same file, and also the file name from the file in a zip archive in viewProfileFromZip in actions/zipped-profiles.js.

My slight concern is that we do have startTime and endTime information in a .cpuprofile file, but I'm not sure what value they are. Do you know? Do you have pointers to where these values are set or to some documentation about those?
I won't say I'm super happy about this. I wish we could use the existing startTime and endTime instead...

I left a few comments otherwise.
Tell me what you think!

julienw · 2023-12-15T15:18:59Z

src/profile-logic/import/chrome.js

+        const timeStampRe =
+          /(\d{4})(\d{2})(\d{2})T(\d{2})(\d{2})(\d{2}).*\.cpuprofile(?:$|\/|\?|#)/;


Suggested change

const timeStampRe =

/(\d{4})(\d{2})(\d{2})T(\d{2})(\d{2})(\d{2}).*\.cpuprofile(?:$|\/|\?|#)/;

const timeStampRe =

/(\d{4})(\d{2})(\d{2})T(\d{2})(\d{2})(\d{2}).*\.cpuprofile\b/;

In a regexp \b means "a word boundary", which is exactly what you're looking for here.

Why do you have this .* between the timestamp and .cpuprofile?

In a regexp \b means "a word boundary", which is exactly what you're looking for here.

I beg to differ, (?:$|\/|\?|#) implements the concept of "end of URL subdirectory" which is more strict than "end of word". In particular, \b treats characters like % and [ as a boundary which could result in profiles being accepted that do not have exactly the .cpuprofile extension (for whatever deliberate reason).

That said, practically there probably isn't much point to be strict about this, and perhaps some people do put additional information on a filename after the file extension. I do prefer that a regex be as strict as possible though.

On the other hand, afaik Firefox Profiler doesn't specifically check for the .cpuprofile extension, instead it looks at the profile's contents to determine profile type. So for consistency, the regex should just match a timestamp i.e. it should just be /(\d{4})(\d{2})(\d{2})T(\d{2})(\d{2})(\d{2})/. What do you think?

Why do you have this .* between the timestamp and .cpuprofile?

The basic filename produced (e.g. CPU-20230928T151126.cpuprofile) is lacking in what the profile is all about, and the current regex already ignores everything before the timestamp. The .* allows the regex to ignore everything after the timestamp before the extension. This is to cater for people who prefer to add identifying information after the timestamp rather than before it.

3c62513 -- now I think it's best to be consistent with the rest of Firefox Profiler that doesn't specially treat the .cpuprofile extension.

251b59c matches on the last timestamp found, just in case someone sticks a timestamp on a folder. I wanted to use String.matchAll(), but Flow 0.96.0 doesn't have a definition for it (!).

julienw · 2023-12-15T17:33:23Z

src/profile-logic/import/chrome.js

+          (profileEvent.args.data.cpuProfile.endTime -
+            profileEvent.args.data.cpuProfile.startTime) /


it's not clear to me that the difference will be in milliseconds. It seems to me this may be tenths of milliseconds, but I'm not so sure.

emm not sure whether I'm getting you here -- it's known that cpuProfile.startTime / .endTime is in microseconds, and one can convert both to milliseconds first before doing the difference (using / 1000), but a / 1000 - b / 1000 is mathematically equivalent to (a - b) / 1000 via algebra, and the latter involves less operations.

If 1 startTime / endTime tick is not actually 1 microsecond though, I suppose there has to be a way to change this assumption.

I would be amazed if there is a startTime / endTime that actually exceeds Number.MAX_SAFE_INTEGER (that would probably be a profile that has a lifespan longer than the average human), but since we require only millisecond precision, I suppose I should convert startTime and endTime to milliseconds first before doing the difference.

0e626fd converted startTime and endTime to milliseconds first but was reverted because I got a test profilingEndTime of 190.7039999961853 (due to floating point rounding error) instead of the correct 190.704.

julienw · 2023-12-15T17:36:09Z

src/profile-logic/import/chrome.js

@@ -678,10 +680,28 @@ async function processTracingEvents(
      }

      if (profileEvent.name === 'CpuProfile') {


I noticed there's a similar if condition above in the same function, where we do also set the threadInfo.lastSeenTime information. I think it would be good to move all of this in the if block above (especially that it's closer to the Profile block too). It would also be good to add a comment to remind the reader about the fact that CpuProfile is added by us in wrapCpuProfileInEvent because it took me 30min to remember that :D

Hopefully will also get to this by early this week (or at least before this week ends).

I noticed there's a similar if condition above in the same function, where we do also set the threadInfo.lastSeenTime information. I think it would be good to move all of this in the if block above (especially that it's closer to the Profile block too).

Done in f1108a4.

It would also be good to add a comment to remind the reader about the fact that CpuProfile is added by us in wrapCpuProfileInEvent ...

Done in 0ba0c39. The ts field should matter?

julienw · 2023-12-15T17:40:17Z

src/profile-logic/import/chrome.js

+        if (match) {
+          const dateTimeString = `${match[1]}-${match[2]}-${match[3]}T${match[4]}:${match[5]}:${match[6]}`;
+          const startTime = new Date(dateTimeString);
+          profile.meta.startTime = startTime.getTime();


Note that startTime represent the moment the main thread started. So it's not great. But I don't see a better option with our current code.

As long as the (adjustable) start time provided is reasonably close to the actual start time, I think it's going to be ok. Support for milliseconds could be added later on for more accuracy.

kazarmy · 2023-12-24T12:55:04Z

Thanks for your patience, while we were busy with other work.

No worries, I'm under resourced too, sometimes terribly so, though partially it's because I don't really prefer focusing on just 1 project/language/topic unless I have to.

We also need to pass the file name from retrieveProfileFromFile in the same file, and also the file name from the file in a zip archive in viewProfileFromZip in actions/zipped-profiles.js.

I'll get to this hopefully sometime early next week.

My slight concern is that we do have startTime and endTime information in a .cpuprofile file, but I'm not sure what value they are. Do you know? Do you have pointers to where these values are set or to some documentation about those?

I actually did some spelunking in the Node V8 source code regarding this, and while I'm not 100% sure (largely because I don't have a Node build environment set up to test whether I'm actually looking at irrelevant duplicate code, and am not looking forward to building Node due to the build times involved), it appears that:

startTime gets its value from a TimeTicks static method (ref, ref, ref).
The TimeTicks class comment states that it is a form of time in microseconds but not convertible to a human-readable time (ref) ...
... probably because its origin is not known in terms of human time (ref).

I didn't get much deeper than that, though it appears that on Windows QueryPerformanceCounter can be involved (ref) which according to this MSDN page, "isn't synchronized to any external time reference".

I won't say I'm super happy about this. I wish we could use the existing startTime and endTime instead...

I'm not happy about this either, but short of persuading the V8 team to record as well the actual system clock time for startTime, I suppose we have to do the recording ourselves.

…nto chrome-profile-start-time

…cting

…e subtracting" This reverts commit 0e626fd.

…nto chrome-profile-start-time

kazarmy · 2023-12-28T16:03:15Z

We also need to pass the file name from retrieveProfileFromFile in the same file, and also the file name from the file in a zip archive in viewProfileFromZip in actions/zipped-profiles.js.

Done in 257485d, tested only manually though.

kazarmy · 2023-12-29T11:08:53Z

Ok, it's ready for review.

…nto chrome-profile-start-time

Previously we were only doing this for CPUProfile profiles. But chrome adds this timestamp to all of its profile files including the Tracing files. See their source code here: https://source.chromium.org/chromium/chromium/src/+/main:third_party/devtools-frontend/src/front_end/panels/timeline/TimelinePanel.ts;l=1242-1251;drc=0cc387000bc7c9369fc34c2f2390d3cbc67f65ab So that's why this commit makes sure that we check the profile url for every type of chrome profiles, and not only for CPU profiles.

…n that We need the profilingStartTime for calculating the time range. That's why we can't simply put zero. But also we need to make sure that profiler frontend reports the correct time. Profiler calculates the recording start timestamp as `startTime + profilingStartTime`. So to be able to tell the user about the correct timestamp we read from the profile file name, we have to calculate the `startTime` like this: `timestamp from name - profilingStartTime`. This commit changes this to make sure that we always show the correct timestamp.

`getEmptyProfile` function already sets the `startTime` to zero.

canova · 2024-11-19T14:25:09Z

Thanks for the PR @kazarmy! It looks great, I tweaked some things and pushed additional commits, mainly to make sure that it works well together with #5187.

The things I've changed:

Make sure that we can accept Trace-<date>.json files to in addition to CPU-<date>.cpuprofile. Since it works for both CPU and Trace json files there is no reason to limit this feature to CPU. See the code here: https://source.chromium.org/chromium/chromium/src/+/main:third_party/devtools-frontend/src/front_end/panels/timeline/TimelinePanel.ts;l=1242-1251;drc=0cc387000bc7c9369fc34c2f2390d3cbc67f65ab
Made sure that profilingStartTime and profilingEndTime works well especially after Compute the profiling start and end time for chrome tracing profiles #5187. Since we didn't have a proper startTime before, it wasn't that important. But now we have to have a correct profilingStartTime to make sure that we choose the right part of the timeline after that PR. So I made sure that we keep both of them, but adjusted the startTime by subtracting profilingStartTime from it to make sure that we get the correct time on the profile info panel.
Applied some small nits.

Here's an example profile

julienw · 2024-11-19T14:32:03Z

src/profile-logic/import/chrome.js

+    // timestamp is of profile save instead of profile start, but one can generate a
+    // more accurate start timestamp through e.g. handling the Chrome DevTools
+    // Protocol `Profiler.consoleProfileStarted` event.


I don't understand how "one" can do something here. Is that something we can do now, or something that could be done in the future?

I think that's the event that's mentioned here: https://chromedevtools.github.io/devtools-protocol/1-2/Profiler/#event-consoleProfileStarted
It's an event that's a part of CDP.

I can't find the same event inside the profile data, so I'm not so sure how to do that. Maybe we can do that for chrome extension. But I'm not so sure, maybe @kazarmy had something else in mind while writing that.

I think that's the event that's mentioned here: https://chromedevtools.github.io/devtools-protocol/1-2/Profiler/#event-consoleProfileStarted

Yes that's the event. I have code (from 11 months ago -- bit-rotted a bit but fortunately can still be made to run) that runs Chrome and attaches to it via https://github.com/cyrus-and/chrome-remote-interface.

Ah I see. We also have this one btw: https://github.com/firefox-devtools/firefox-profiler-for-chrome We recently published it on the Chrome Web Store. That's why I was spending some time on improving the importer.
(It's not an alternative to the one you linked, just another way to visualize the data)

Oh cool! I do prefer to programmatically start the Chrome profiler if possible, though I understand this might not be the best way to spend precious engineer time in a work environment.

julienw

Thanks @kazarmy and @canova !
This looks pretty good to me, let's land this!

@canova please use a merge commit so that we retain the commits from both of you as well as the useful commit logs.

kazarmy · 2024-11-19T15:02:41Z

Thanks! 🎉

[Julien Wajsberg] Fix the network bars not being properly positioned in Chrome (#5209) [Nazım Can Altınova] Only show the NavigationStart in the timeline if it has innerWindowID (#5210) [Nisarg Jhaveri] Fix loading and error messages for /from-post-message (#5175) [Khairul Azhar Kasmiran] Chrome `.cpuprofile` importer: Get profile start time from URL (Chrome DevTools UI format) (#4797) [Khairul Azhar Kasmiran] Remove "Recording started" line from Profile Info if startTime is 0 (#5219) [Sean Kim] Add HTTP protocol version for a request in the profiler network tab (#5206) [Julien Wajsberg] Switch to a maintained fork of npm-run-all (#5221) [Nicolas Chevobbe] Adapt Tabs in High Contrast Mode (#5220) [Markus Stange] Fix test debugging in VS Code. (#5227) [Julien Wajsberg] Added appropriate null check to handle missing unified string optional values (#5192) And thanks to our localizers: de: Michael Köhler el: Jim Spentzos en-CA: chutten en-GB: Ian Neal es-CL: ravmn fy-NL: Fjoerfoks ia: Melo46 it: Michele Rodaro kab: ZiriSut nl: Mark Heijl pt-BR: Marcelo Ghelman ru: Valery Ledovskoy sv-SE: Andreas Pettersson tr: Grk zh-CN: Olvcpr423 zh-TW: Pin-guang Chen

Chrome .cpuprofile importer: Get profile start time from URL (Chrom…

1f92eb0

…e DevTools UI format)

kazarmy force-pushed the chrome-profile-start-time branch from 2eeb84d to 1f92eb0 Compare November 11, 2023 09:08

julienw requested review from julienw and canova November 16, 2023 14:57

Merge branch 'main' of https://github.com/firefox-devtools/profiler i…

5c5cab1

…nto chrome-profile-start-time

kazarmy force-pushed the chrome-profile-start-time branch from 697460e to 444a45e Compare November 20, 2023 15:19

Pass profileUrl into unserializeProfileOfArbitraryFormat() and ad…

77ebebf

…d test

kazarmy force-pushed the chrome-profile-start-time branch from 444a45e to 77ebebf Compare November 20, 2023 15:28

kazarmy added 2 commits November 21, 2023 18:27

Merge branch 'main' of https://github.com/firefox-devtools/profiler i…

db2966b

…nto chrome-profile-start-time

Wrap comment properly

9ea1253

Merge branch 'main' of https://github.com/firefox-devtools/profiler i…

e8334ba

…nto chrome-profile-start-time

kazarmy marked this pull request as draft November 24, 2023 00:41

kazarmy marked this pull request as ready for review November 24, 2023 01:06

kazarmy added 4 commits December 3, 2023 22:14

Merge branch 'main' of https://github.com/firefox-devtools/profiler i…

be10314

…nto chrome-profile-start-time

Merge branch 'main' of https://github.com/firefox-devtools/profiler i…

49834cb

…nto chrome-profile-start-time

Merge branch 'main' of https://github.com/firefox-devtools/profiler i…

46eaa0b

…nto chrome-profile-start-time

Update snapshot

ee1da96

julienw reviewed Dec 15, 2023

View reviewed changes

kazarmy added 3 commits December 26, 2023 20:20

Merge branch 'main' of https://github.com/firefox-devtools/profiler i…

89ee2c2

…nto chrome-profile-start-time

Use minimal regex for timestamp

3c62513

Convert startTime and endTime to milliseconds first before subtra…

0e626fd

…cting

kazarmy marked this pull request as draft December 26, 2023 12:53

kazarmy added 2 commits December 26, 2023 21:00

Revert "Convert startTime and endTime to milliseconds first befor…

05469ab

…e subtracting" This reverts commit 0e626fd.

Match on last timestamp found

251b59c

kazarmy added 2 commits December 28, 2023 23:48

Merge branch 'main' of https://github.com/firefox-devtools/profiler i…

675a931

…nto chrome-profile-start-time

Pass file name in retrieveProfileFromFile and viewProfileFromZip

257485d

Combine 'CpuProfile' if blocks

f1108a4

kazarmy marked this pull request as ready for review December 29, 2023 11:08

Add comment on wrapCpuProfileInEvent wrapping the CpuProfile

0ba0c39

kazarmy force-pushed the chrome-profile-start-time branch from 2982534 to 0ba0c39 Compare December 29, 2023 11:12

julienw self-requested a review January 19, 2024 17:53

kazarmy added 2 commits January 28, 2024 18:11

Merge branch 'main' of https://github.com/firefox-devtools/profiler i…

f28d3a3

…nto chrome-profile-start-time

Merge branch 'main' of https://github.com/firefox-devtools/profiler i…

3b16920

…nto chrome-profile-start-time

julienw mentioned this pull request Oct 7, 2024

Chrome profiles are shown with 1/1/1970 datestamp (prominently in tab title) #3849

Closed

julienw mentioned this pull request Nov 5, 2024

Compute the profiling start and end time for chrome tracing profiles #5187

Merged

kazarmy and others added 10 commits November 7, 2024 20:51

Merge branch 'main' of https://github.com/firefox-devtools/profiler i…

3891c79

…nto chrome-profile-start-time

Update test snapshot

847bbd1

Merge branch 'main' of https://github.com/firefox-devtools/profiler i…

37827e2

…nto chrome-profile-start-time

Bump versions in test snapshot

84eb75c

Merge branch 'main' into chrome-profile-start-time

b339a3f

Add a comment to explain we get the last timestamp

cf57d2f

Give proper names to matches for easy reading

f0e562c

Remove the unnecessary else block

b262540

`getEmptyProfile` function already sets the `startTime` to zero.

julienw reviewed Nov 19, 2024

View reviewed changes

julienw approved these changes Nov 19, 2024

View reviewed changes

canova merged commit 8764e83 into firefox-devtools:main Nov 19, 2024
18 checks passed

canova mentioned this pull request Nov 27, 2024

Deploy Nov 27, 2024 #5231

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Chrome `.cpuprofile` importer: Get profile start time from URL (Chrome DevTools UI format) #4797

Chrome `.cpuprofile` importer: Get profile start time from URL (Chrome DevTools UI format) #4797

kazarmy commented Nov 11, 2023 •

edited by data-sync-user

Loading

codecov bot commented Nov 11, 2023 •

edited

Loading

kazarmy commented Nov 11, 2023

kazarmy commented Nov 20, 2023

julienw commented Nov 23, 2023

kazarmy commented Nov 24, 2023

julienw left a comment

julienw Dec 15, 2023

kazarmy Dec 25, 2023

kazarmy Dec 26, 2023

kazarmy Dec 27, 2023

julienw Dec 15, 2023

kazarmy Dec 25, 2023

kazarmy Dec 25, 2023 •

edited

Loading

kazarmy Dec 26, 2023

julienw Dec 15, 2023

kazarmy Dec 25, 2023

kazarmy Dec 29, 2023 •

edited

Loading

julienw Dec 15, 2023

kazarmy Dec 25, 2023

kazarmy commented Dec 24, 2023

kazarmy commented Dec 28, 2023

kazarmy commented Dec 29, 2023

canova commented Nov 19, 2024 •

edited

Loading

julienw Nov 19, 2024

canova Nov 19, 2024

kazarmy Nov 19, 2024

canova Nov 19, 2024 •

edited

Loading

kazarmy Nov 19, 2024

julienw left a comment

kazarmy commented Nov 19, 2024

		const timeStampRe =
		/(\d{4})(\d{2})(\d{2})T(\d{2})(\d{2})(\d{2}).*\.cpuprofile(?:$\|\/\|\?\|#)/;

		(profileEvent.args.data.cpuProfile.endTime -
		profileEvent.args.data.cpuProfile.startTime) /

		@@ -678,10 +680,28 @@ async function processTracingEvents(
		}

		if (profileEvent.name === 'CpuProfile') {

Chrome .cpuprofile importer: Get profile start time from URL (Chrome DevTools UI format) #4797

Chrome .cpuprofile importer: Get profile start time from URL (Chrome DevTools UI format) #4797

Conversation

kazarmy commented Nov 11, 2023 • edited by data-sync-user Loading

codecov bot commented Nov 11, 2023 • edited Loading

Codecov Report

kazarmy commented Nov 11, 2023

kazarmy commented Nov 20, 2023

julienw commented Nov 23, 2023

kazarmy commented Nov 24, 2023

julienw left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kazarmy Dec 25, 2023 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kazarmy Dec 29, 2023 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kazarmy commented Dec 24, 2023

kazarmy commented Dec 28, 2023

kazarmy commented Dec 29, 2023

canova commented Nov 19, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

canova Nov 19, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

julienw left a comment

Choose a reason for hiding this comment

kazarmy commented Nov 19, 2024

Chrome `.cpuprofile` importer: Get profile start time from URL (Chrome DevTools UI format) #4797

Chrome `.cpuprofile` importer: Get profile start time from URL (Chrome DevTools UI format) #4797

kazarmy commented Nov 11, 2023 •

edited by data-sync-user

Loading

codecov bot commented Nov 11, 2023 •

edited

Loading

kazarmy Dec 25, 2023 •

edited

Loading

kazarmy Dec 29, 2023 •

edited

Loading

canova commented Nov 19, 2024 •

edited

Loading

canova Nov 19, 2024 •

edited

Loading