You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow the stackTable.frame column to contain an Int32Array.
This is the first typed array that we're supporting inside the profile
format.
When a profile is saved in the JsonSlabs format, it will now have this
column as a separate slab that doesn't require JSON parsing.
Profile compacting now always turns `stackTable.frame` into a typed array,
even if that column was a regular JS array in the input profile.
We still allow a regular JSON array here, because profiles stored as JSON
cannot contain typed arrays, and we want to use the same type definition
for JSON and JSLB profiles.
Here's how this change impacts profile sizes and loading times on
this profile: https://storage.googleapis.com/profiler-get-symbols-fixtures/large-speedometer3-profile.json.gz
| Version | .jslb.gz size | .jslb size | Load time | Profile of it loading |
|---------|---------------|------------|-------------|-----------------------------------|
| 64 | 122 MB | 605 MB | 7.6 seconds | https://share.firefox.dev/4ogUKba |
| 65 | 125 MB | 544 MB | 6.0 seconds | https://share.firefox.dev/3Qopiem |
The compressed size has grown a small bit, but the other savings are significant:
- We no longer have 131 MB of text for the frame column in the JSON - the frame column
is now stored in a 70 MB i32 slab.
- Less time in GZ decompression, because the uncompressed size is now smaller.
- There is a lot less time spent in TextDecoder.decode and JSON.parse, because we're
no longer decoding and parsing 131 MB of text for the frame column.
Copy file name to clipboardExpand all lines: docs-developer/CHANGELOG-formats.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,10 @@ Note that this is not an exhaustive list. Processed profile format upgraders can
6
6
7
7
## Processed profile format
8
8
9
+
### Version 65
10
+
11
+
The stack table's `frame` column (stored at `profile.shared.stackTable.frame`) can now optionally be stored as an `Int32Array`, for profiles loaded from [JsonSlabs](https://github.com/mstange/json-slabs/) files (.jslb, .jslb.gz). Regular JS / JSON arrays are still accepted.
12
+
9
13
### Version 64
10
14
11
15
A new `SourceLocationTable` has been added to `profile.shared.sourceLocationTable`. It holds the original (pre-compilation) source positions produced by source map symbolication, paired with the generated `line`/`column` already on `FrameTable`.
0 commit comments