1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
|
====
AWSY
====
Are We Slim Yet project (commonly known as AWSY) tracks memory usage across builds.
On treeherder, the AWSY builds are listed in subgroups of `SY`.
AWSY tests consist of three types: TP5*, TP6, and Base Memory Usage.
*\*TP5 tests are out of date and no longer maintained. These tests are scheduled to be removed:* https://bugzilla.mozilla.org/show_bug.cgi?id=1712406
Awsy tests
----------
.. dropdown:: base (FF)
:class-container: anchor-id-base-Awsy-tests
* Command to Run Locally
.. code-block::
./mach awsy-test --base
**Owner**: :mccr8 and Perftest Team
* **Test Task**:
* test-linux1804-64-clang-trunk-qr/opt
* awsy-base: None
* awsy-base-dmd: None
* test-linux1804-64-qr/opt
* awsy-base: None
* awsy-base-dmd: None
* test-linux1804-64-shippable-qr/opt
* awsy-base: trunk
* awsy-base-dmd: None
* test-macosx1470-64-shippable/opt
* awsy-base: trunk
* awsy-base-dmd: None
* test-windows11-64-24h2-shippable/opt
* awsy-base: trunk
* awsy-base-dmd: None
* test-windows11-64-24h2/opt
* awsy-base: None
* awsy-base-dmd: None
.. dropdown:: dmd (FF)
:class-container: anchor-id-dmd-Awsy-tests
* Command to Run Locally
.. code-block::
./mach awsy-test --dmd
**Owner**: :mccr8 and Perftest Team
* **Test Task**:
* test-linux1804-64-clang-trunk-qr/opt
* awsy-base-dmd: None
* awsy-dmd: None
* test-linux1804-64-qr/opt
* awsy-base-dmd: None
* awsy-dmd: None
* test-linux1804-64-shippable-qr/opt
* awsy-base-dmd: None
* awsy-dmd: None
* test-macosx1470-64-shippable/opt
* awsy-base-dmd: None
* awsy-dmd: None
* test-windows11-64-24h2-shippable/opt
* awsy-base-dmd: None
* awsy-dmd: None
* test-windows11-64-24h2/opt
* awsy-base-dmd: None
* awsy-dmd: None
.. dropdown:: tp5 (FF)
:class-container: anchor-id-tp5-Awsy-tests
* Command to Run Locally
.. code-block::
./mach awsy-test --tp5
**Owner**: :mccr8 and Perftest Team
* **Test Task**:
* test-linux1804-64-clang-trunk-qr/opt
* test-linux1804-64-qr/opt
* test-linux1804-64-shippable-qr/opt
* test-macosx1470-64-shippable/opt
* test-windows11-64-24h2-shippable/opt
* test-windows11-64-24h2/opt
.. dropdown:: tp6 (FF)
:class-container: anchor-id-tp6-Awsy-tests
* Command to Run Locally
.. code-block::
./mach awsy-test
**Owner**: :mccr8 and Perftest Team
* **Test Task**:
* test-linux1804-64-clang-trunk-qr/opt
* awsy-tp6: None
* test-linux1804-64-qr/opt
* awsy-tp6: None
* test-linux1804-64-shippable-qr/opt
* awsy-tp6: trunk
* test-macosx1470-64-shippable/opt
* awsy-tp6: trunk
* test-windows11-64-24h2-shippable/opt
* awsy-tp6: trunk
* test-windows11-64-24h2/opt
* awsy-tp6: None
Running AWSY Locally
*********************
Running tests locally is most likely only useful for debugging what is going on in a test,
as the test output is only reported as raw JSON. The CLI is documented via:
.. code-block:: bash
./mach awsy-test --help
*Currently all tests will download TP5 even if it is not used, see:* https://bugzilla.mozilla.org/show_bug.cgi?id=1683920
TP5 tests
=========
.. code-block:: bash
./mach awsy-test --tp5
TP6 tests
=========
.. code-block:: bash
./mach awsy-test
Base Memory Usage tests
========================
.. code-block:: bash
./mach awsy-test --base
Running AWSY on Try
********************
AWSY runs can be generated through the mach try fuzzy finder:
.. code-block:: bash
./mach try fuzzy
A query for "awsy" will return all AWSY tests. The default test is TP5, TP6 and Base test names will contain `tp6` and `base`, respectively.
The following documents all tests we currently run for AWSY.
*The following content was migrated from* https://wiki.mozilla.org/AWSY/Tests *and will be updated to clarify TP5/TP6 tests vs Base tests:* https://bugzilla.mozilla.org/show_bug.cgi?id=1714600
TP5/TP6 Tests
**************
The following tests exist for both TP5 and TP6. Running `./mach awsy-test` by default will run TP6 tests*.
To run TP5 tests, add the `--tp5` flag: `./mach awsy-test --tp5`
*\*TP5 tests are out of date and no longer maintained. These tests are scheduled to be removed:* https://bugzilla.mozilla.org/show_bug.cgi?id=1712406
Explicit Memory
================
* This is memory explicitly reported by a memory reporter. It includes all the memory allocated via explicit calls to heap allocation functions (such as malloc and new), and some (only that covered by memory reporters) of the memory allocated via explicit calls to non-heap allocation functions (such as mmap and VirtualAlloc).
**Possible regression causes**
* A regression in this usually means a new feature is using or retaining more memory and should be looked at. These are easier to diagnose because we can compare memory reports.
See the `about:memory` `mdn page <https://developer.mozilla.org/docs/Mozilla/Performance/about:memory#Explicit_Allocations>`__ for more details.
Heap Unclassified
==================
*to do: add test definition*
Images
=======
* This is a subset of the "explicit" measurement that focuses on memory used to render images.
**Possible regression causes**
* A regression in this can indicate leaks or poor memory usage in the image subsystem. In the past this was a persistent problem.
JS
====
*to do: add test definition*
Resident Memory
================
* This is a higher level measurement provided by the operating system. We sum the "resident" memory (`RSS <https://en.wikipedia.org/wiki/Resident_set_size>`_) with the `resident-unique <https://en.wikipedia.org/wiki/Unique_set_size>`_ memory of the content processes. It's pretty noisy and large so it's not very useful in detecting smaller regressions.
**Possible regression causes**
* Regressions in this often track regressions in explicit and heap unclassified. If we see a regression in resident, but not in other reports this can indicate we are leaking untracked memory (perhaps through shared memory, graphics allocations, file handles, etc).
Base Content Tests
*******************
* An updated test focused on supporting Fission. This measures the base overhead of an empty content process. It tracks resident unique, heap unclassified, JS, and explicit memory metrics as well as storing full memory reports as artifacts. The median value for each metric is used from across all content processes. It has much lower thresholds for alerting and is recorded in `Perfherder <https://wiki.mozilla.org/EngineeringProductivity/Projects/Perfherder>`_.
Base Content Explicit
======================
**Possible regression causes**
A change has caused more JavaScript to load at startup or into blank pages.
* **Common solution**: lazily load any new modules you rely on
* **Common solution**: Split your code out to only load what is minimally needed initially. You modified the JS engine and it's using more memory
* **Common solution**: Attempt to reduce your object size for the common case, these tend to add up! You implemented a new feature in JavaScript
* **Common solution**: Write the majority (or all of it) in compiled code (C++/Rust). This will reduce overhead and generally improve performance.
Base Content Heap Unclassified
===============================
* The "heap-unclassified" value represents heap-allocated memory that is not measured by any memory reporter. This is typically 10-20% of "explicit".
**Possible regression causes**
* A regression in this can indicate that we're leaking memory or that additional memory reporters should be added.
* An improvement can indicate that leaks have been fixed or that we added new memory reporters.
See the `about:memory` `mdn page <https://developer.mozilla.org/docs/Mozilla/Performance/about:memory#Explicit_Allocations>`__ for more details.
Base Content JS
================
* This is the "js-main-runtime/" value in `about:memory` which is all the memory attributed to the javascript engine.
**Possible regression causes**
* A regression in this number can indicate leaks in the JS engine, optimizations that take performance into consideration at the expense of more memory, or problems with the garbage collector.
Base Content Resident Unique Memory
====================================
*to do: add test definition*
Other references
-----------------
`Are We Slim Yet MDN web docs <https://developer.mozilla.org/en-US/docs/Mozilla/Performance/AWSY>`_
|
