profile-viewer 0.0.3 → 0.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/dist/029b9e4fd0218d7b09c6.svg +8 -0
- data/dist/{f0599659345cf76717cd.svg → 118632062f4755918dac.svg} +1 -1
- data/dist/{136.4ad3301b8aacf759ea70.bundle.js → 136.ad4176dc2a8e5cf33ef3.bundle.js} +2 -2
- data/dist/{136.4ad3301b8aacf759ea70.bundle.js.map → 136.ad4176dc2a8e5cf33ef3.bundle.js.map} +1 -1
- data/dist/{171.621b9df5978342be5662.bundle.js → 171.37d1e1824587d8df0ae2.bundle.js} +2 -2
- data/dist/{171.621b9df5978342be5662.bundle.js.map → 171.37d1e1824587d8df0ae2.bundle.js.map} +1 -1
- data/dist/234ed61ab185caff67e3.svg +8 -0
- data/dist/280.4edd20bd6228986bbf2e.bundle.js +2 -0
- data/dist/280.4edd20bd6228986bbf2e.bundle.js.map +1 -0
- data/dist/{79eaad4fc0c398100809.svg → 3a829bf1fcf02598aa4b.svg} +1 -1
- data/dist/556.b8d3d4d402ced081615a.bundle.js +2 -0
- data/dist/{556.2be67a37a0c61fdc2485.bundle.js.map → 556.b8d3d4d402ced081615a.bundle.js.map} +1 -1
- data/dist/874.7cb94ee0732c5a2ca826.bundle.js +2 -0
- data/dist/874.7cb94ee0732c5a2ca826.bundle.js.map +1 -0
- data/dist/8846b19a497771fe0e9d.svg +4 -0
- data/dist/957.2f40be4cef3037bc352b.bundle.js +3 -0
- data/dist/957.2f40be4cef3037bc352b.bundle.js.LICENSE.txt +19 -0
- data/dist/957.2f40be4cef3037bc352b.bundle.js.map +1 -0
- data/dist/999.a1119c25d77e1883c1e1.bundle.js +2 -0
- data/dist/999.a1119c25d77e1883c1e1.bundle.js.map +1 -0
- data/dist/docs/_navbar.md +3 -3
- data/dist/docs/_sidebar.md +28 -28
- data/dist/docs/advanced-topics.md +5 -5
- data/dist/docs/async-posix-signal-control.md +5 -6
- data/dist/docs/bunny-2.md +3 -2
- data/dist/docs/bunny.md +29 -26
- data/dist/docs/gitpod.md +5 -10
- data/dist/docs/guide-android-profiling.md +18 -2
- data/dist/docs/guide-filtering-call-trees.md +11 -11
- data/dist/docs/guide-getting-started.md +4 -5
- data/dist/docs/guide-perf-profiling.md +8 -8
- data/dist/docs/guide-profiling-android-directly-on-device.md +14 -13
- data/dist/docs/guide-profiling-firefox-android.md +2 -3
- data/dist/docs/guide-remote-profiling.md +24 -23
- data/dist/docs/guide-removing-profiler.md +1 -0
- data/dist/docs/guide-stack-samples-and-call-trees.md +2 -0
- data/dist/docs/guide-startup-shutdown.md +14 -9
- data/dist/docs/guide-ui-tour-panels.md +4 -3
- data/dist/docs/guide-ui-tour-timeline.md +3 -0
- data/dist/docs/index.html +21 -18
- data/dist/docs/ipc-messages.md +6 -6
- data/dist/docs/js/docsify_v4.12.2+.min.js +1 -1
- data/dist/docs/memory-allocations.md +28 -6
- data/dist/docs/videos.md +10 -10
- data/dist/index.html +1 -1
- data/dist/locales/be/app.ftl +108 -0
- data/dist/locales/de/app.ftl +20 -0
- data/dist/locales/el/app.ftl +36 -11
- data/dist/locales/en-CA/app.ftl +29 -5
- data/dist/locales/en-GB/app.ftl +25 -5
- data/dist/locales/en-US/app.ftl +23 -4
- data/dist/locales/es-CL/app.ftl +19 -2
- data/dist/locales/fr/app.ftl +61 -0
- data/dist/locales/fur/app.ftl +16 -0
- data/dist/locales/fy-NL/app.ftl +20 -0
- data/dist/locales/ia/app.ftl +14 -0
- data/dist/locales/it/app.ftl +14 -0
- data/dist/locales/kab/app.ftl +19 -0
- data/dist/locales/nl/app.ftl +20 -0
- data/dist/locales/pt-BR/app.ftl +14 -0
- data/dist/locales/ru/app.ftl +20 -0
- data/dist/locales/sv-SE/app.ftl +20 -0
- data/dist/locales/tr/app.ftl +52 -0
- data/dist/locales/uk/app.ftl +20 -0
- data/dist/locales/zh-CN/app.ftl +18 -3
- data/dist/locales/zh-TW/app.ftl +61 -47
- data/dist/main.6cdc9308b67c00785584.bundle.js +198 -0
- data/dist/{main.ac7130d34ce3b872712a.bundle.js.LICENSE.txt → main.6cdc9308b67c00785584.bundle.js.LICENSE.txt} +2 -2
- data/dist/main.6cdc9308b67c00785584.bundle.js.map +1 -0
- data/dist/photon/{f0599659345cf76717cd.svg → 118632062f4755918dac.svg} +1 -1
- data/dist/photon/index.html +1 -1
- data/dist/photon/main.e1d25e5ea6d5812b127b.bundle.js +2 -0
- data/dist/photon/main.e1d25e5ea6d5812b127b.bundle.js.map +1 -0
- data/dist/sw.js +1 -1
- data/dist/sw.js.map +1 -1
- data/ruby-bin/profile-viewer +10 -1
- data/ruby-bin/profile-viewer-version.rb +1 -1
- metadata +29 -25
- data/dist/280.b4210a48e650408000c3.bundle.js +0 -2
- data/dist/280.b4210a48e650408000c3.bundle.js.map +0 -1
- data/dist/556.2be67a37a0c61fdc2485.bundle.js +0 -2
- data/dist/874.2a087b9b5a296a9c3fcd.bundle.js +0 -2
- data/dist/874.2a087b9b5a296a9c3fcd.bundle.js.map +0 -1
- data/dist/b805360fcc91834556c9.svg +0 -4
- data/dist/main.ac7130d34ce3b872712a.bundle.js +0 -201
- data/dist/main.ac7130d34ce3b872712a.bundle.js.map +0 -1
- data/dist/photon/main.aafbcdad3fb08c7ae5b4.bundle.js +0 -2
- data/dist/photon/main.aafbcdad3fb08c7ae5b4.bundle.js.map +0 -1
|
@@ -32,10 +32,11 @@ inside the selected function.
|
|
|
32
32
|
|
|
33
33
|
The Flame Graph provide a more visual view into the very same call tree
|
|
34
34
|
structures:
|
|
35
|
-
|
|
36
|
-
|
|
35
|
+
|
|
36
|
+
- Larger rectangles mean more running time.
|
|
37
|
+
- The rectangles at the top are the stacks contributing to the self time, that
|
|
37
38
|
is the code where the program actually spends time.
|
|
38
|
-
|
|
39
|
+
- The order is always the same, which makes it more convenient to compare
|
|
39
40
|
between different range selections, but also between different profiles.
|
|
40
41
|
|
|
41
42
|
Some users will prefer using the flame graph over the call tree because it's
|
|
@@ -47,6 +47,7 @@ Perhaps one of the most useful markers is the responsiveness marker—pictured h
|
|
|
47
47
|
Only certain markers are broken out and colored in the timeline. A similar but more detailed view can be seen in the Marker Chart panel.
|
|
48
48
|
|
|
49
49
|
## Timeline's network activity
|
|
50
|
+
|
|
50
51
|
|
|
51
52
|
|
|
52
53
|
Network requests are displayed in the timeline, which can be useful to correlate
|
|
@@ -58,6 +59,7 @@ Hovering a network request will show interesting information about it, and
|
|
|
58
59
|
clicking it will switch to the more detailed network panel.
|
|
59
60
|
|
|
60
61
|
## Timeline's memory usage change
|
|
62
|
+
|
|
61
63
|
|
|
62
64
|
|
|
63
65
|
The timeline also gives an overview of the memory usage change for a process.
|
|
@@ -66,6 +68,7 @@ difference between the lowest and highest memory usage during the profiling
|
|
|
66
68
|
session.
|
|
67
69
|
|
|
68
70
|
## Track selection
|
|
71
|
+
|
|
69
72
|
|
|
70
73
|
|
|
71
74
|
With the button right above the tracks it's possible to either hide tracks and
|
data/dist/docs/index.html
CHANGED
|
@@ -1,21 +1,24 @@
|
|
|
1
|
-
<!
|
|
1
|
+
<!doctype html>
|
|
2
2
|
<html lang="en">
|
|
3
|
-
<head>
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
<
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
3
|
+
<head>
|
|
4
|
+
<meta charset="UTF-8" />
|
|
5
|
+
<title>Firefox Profiler - Documentation</title>
|
|
6
|
+
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
|
|
7
|
+
<meta
|
|
8
|
+
name="description"
|
|
9
|
+
content="Documentation related to the Firefox Profiler, a tool to record and visualize profile."
|
|
10
|
+
/>
|
|
11
|
+
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
|
12
|
+
<link rel="stylesheet" href="css/vue_v4.12.2.min.css" />
|
|
13
|
+
<link rel="stylesheet" href="css/style-overrides.css" />
|
|
14
|
+
</head>
|
|
15
|
+
<body>
|
|
16
|
+
<div id="app"></div>
|
|
17
|
+
<script src="js/init.js"></script>
|
|
18
|
+
<!-- This includes a fix in docsify for pages with more than 1 video.
|
|
16
19
|
See https://github.com/docsifyjs/docsify/pull/1824 -->
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
</body>
|
|
20
|
+
<script src="js/docsify_v4.12.2+.min.js"></script>
|
|
21
|
+
<script src="js/ga_v4.12.2.min.js"></script>
|
|
22
|
+
<script src="js/search_v4.12.2.min.js"></script>
|
|
23
|
+
</body>
|
|
21
24
|
</html>
|
data/dist/docs/ipc-messages.md
CHANGED
|
@@ -20,12 +20,12 @@ Hovering over a marker for an IPC message will provide more details about it:
|
|
|
20
20
|
Each IPC message has several durations associated with it, corresponding to the
|
|
21
21
|
spans of time between consecutive IPC message phases as described above:
|
|
22
22
|
|
|
23
|
-
|
|
23
|
+
- _Send thread latency_: the time between `SendXXX` being called and the first
|
|
24
24
|
byte sent over the IPC channel
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
channel and the last byte being
|
|
28
|
-
|
|
25
|
+
- _IPC send duration_: the time taken to send all the bytes over the IPC channel
|
|
26
|
+
- _IPC recv latency_: the time between the last byte being sent over the IPC
|
|
27
|
+
channel and the last byte being _received_
|
|
28
|
+
- _Recv thread latency_: the time between the last byte being received from the
|
|
29
29
|
IPC channel and the `RecvXXX` function being called
|
|
30
30
|
|
|
31
31
|
## Enabling the Feature
|
|
@@ -38,7 +38,7 @@ In `about:profiling`, scroll down to the `Features` section and enable the
|
|
|
38
38
|
### Profiling the IO Threads
|
|
39
39
|
|
|
40
40
|
By default, the sender's and recipient's IO threads aren't included in a
|
|
41
|
-
profile. To include these, add `Gecko_IOThread` and
|
|
41
|
+
profile. To include these, add `Gecko_IOThread` and `Chrome_ChildThread` to the
|
|
42
42
|
list of threads to be profiled.
|
|
43
43
|
|
|
44
44
|
|