Various logs say: - [m-c 1](https://treeherder.mozilla.org/logviewer?job_id=462001761&repo=mozilla-central&lineNumber=15964): `[task 2024-06-12T12:19:07.515Z] 12:19:07 INFO - QM says usage of https://test1.example.org is 127368` - [m-c 2](https://treeherder.mozilla.org/logviewer?job_id=461984918&repo=mozilla-central&lineNumber=92104): `[task 2024-06-12T10:35:08.785Z] 10:35:08 INFO - QM says usage of https://test1.example.org is 127368` So that's 31 4k pages and a few extra bytes which is interesting. This might be a good reason to implement the granular quota usage report, potentially with even more data available to chrome callers, since it's possible there's some transient aspects to this.
Bug 1776004 Comment 121 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Various logs say: - [m-c 1](https://treeherder.mozilla.org/logviewer?job_id=462001761&repo=mozilla-central&lineNumber=15964): `[task 2024-06-12T12:19:07.515Z] 12:19:07 INFO - QM says usage of https://test1.example.org is 127368` - [m-c 2](https://treeherder.mozilla.org/logviewer?job_id=461984918&repo=mozilla-central&lineNumber=92104): `[task 2024-06-12T10:35:08.785Z] 10:35:08 INFO - QM says usage of https://test1.example.org is 127368` - Same thing for at least 5 autoland logs. So that's 31 4k pages and a few extra bytes which is interesting. This might be a good reason to implement the granular quota usage report, potentially with even more data available to chrome callers, since it's possible there's some transient aspects to this that other mechanisms like exporting the origin directory might not be able to meaningfully capture.