Npm run format
This commit is contained in:
Родитель
f8d0243eb2
Коммит
91f08fed68
|
@ -49,7 +49,7 @@ Currently, the best way to introspect the internals of `StudyTelemetryPacket` is
|
||||||
|
|
||||||
## Performance optimizations affecting submitted telemetry
|
## Performance optimizations affecting submitted telemetry
|
||||||
|
|
||||||
* Most OpenWPM events are grouped into batches under their corresponding [web navigations](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webNavigation) (https://github.com/motin/jestr-pioneer-shield-study/issues/10), diminishing performance penalties associated with submitting many small packages via Pioneer telemetry.
|
- Most OpenWPM events are grouped into batches under their corresponding [web navigations](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webNavigation) (https://github.com/motin/jestr-pioneer-shield-study/issues/10), diminishing performance penalties associated with submitting many small packages via Pioneer telemetry.
|
||||||
* A [500kb ping size limit](https://github.com/motin/jestr-pioneer-shield-study/issues/1) applies to the sum of all http and js packets in a particular web navigation, decreasing the overall ping data volume [while still retaining as much relevant data as possible](https://github.com/motin/jestr-pioneer-shield-study/issues/11). Effective limits on navigation-specific telemetry payloads are now being determined by either the 500kb size limit, 10 second duration cutoff and 1000 events (whichever limit is hit first)
|
- A [500kb ping size limit](https://github.com/motin/jestr-pioneer-shield-study/issues/1) applies to the sum of all http and js packets in a particular web navigation, decreasing the overall ping data volume [while still retaining as much relevant data as possible](https://github.com/motin/jestr-pioneer-shield-study/issues/11). Effective limits on navigation-specific telemetry payloads are now being determined by either the 500kb size limit, 10 second duration cutoff and 1000 events (whichever limit is hit first)
|
||||||
|
|
||||||
If no limit was hit, the telemetry payload will include a non-empty `navigationBatch` property. If a limit was hit, a telemetry payload with `trimmedNavigationBatch` will be submitted instead.
|
If no limit was hit, the telemetry payload will include a non-empty `navigationBatch` property. If a limit was hit, a telemetry payload with `trimmedNavigationBatch` will be submitted instead.
|
||||||
|
|
Загрузка…
Ссылка в новой задаче