Add disk space measurements to Telemetry

RESOLVED WONTFIX

Status

()

Toolkit
Telemetry
RESOLVED WONTFIX
3 years ago
2 days ago

People

(Reporter: gfritzsche, Unassigned)

Tracking

(Blocks: 2 bugs)

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox45 affected)

Details

For the hardware survey, the following measurements are requested and not present in Telemetry yet:
* total hard drive space
* free hard drive space
Potential dupe: bug 707402, which is specifically about the free space on the disk cache device on startup.
Open questions:

* What exact question is this supposed to answer? Local storage space available to web apps / web games?
* If so, is it sufficient to submit the available space for only the disk that is used for local storage?
* Do we actually need total space for something specific?
Want Luke's feedback, but I think:

We are looking for available space where a user can install a game. Which should help developers know how large a size they can target on average.

I think it's sufficient to do only the space available in local storage, since that's where the games go. But, want to make sure Luke can't think of a reason we might also want to track total storage as well? It might be interesting to track total storage over time?
Flags: needinfo?(luke)

Comment 4

3 years ago
Ultimately, GetTemporaryStorageLimit() (http://mxr.mozilla.org/mozilla-central/source/dom/quota/ActorsParent.cpp#1918) calls GetDiskSpaceAvailable() on the 'storage' dir (which I believe is always inside the profile dir (Jan?)) and this basically limits the storage available to the webapp dev.  Now, some of the non-free space is controlled by the QuotaManager and can be evicted, so it seems we'd get the clearest picture with:
 - total size of drive containing storage dir (to provide context for the next two figures)
 - amount of free space + amount we could evict (aCurrentUsage in GetTemporaryStorageLimit)
 - amount of free space

Jan, does this all make sense?  Our goal is to get a picture of how much webapps in the wild could expect to store (ignoring our heuristics that further clamp quota, since those are subject and likely to change).
Flags: needinfo?(luke) → needinfo?(Jan.Varga)

Comment 5

3 years ago
Yeah, that makes sense, Luke.
Flags: needinfo?(Jan.Varga)

Comment 6

3 years ago
Jan: when we get actual UX for evicting permanent storage, would we be able to track total permanent storage usage (the way we track temporary storage now) so that it could be included in the aCurrentUsage figure above?

Comment 7

3 years ago
(In reply to Luke Wagner [:luke] from comment #6)
> Jan: when we get actual UX for evicting permanent storage, would we be able
> to track total permanent storage usage (the way we track temporary storage
> now) so that it could be included in the aCurrentUsage figure above?

We don't track permanet storage usage since it's unlimited, but we can get usage for specific origin on demand by calling QuotaManagerService::GetUsageForPrincipal(). This is probably not very helpful in this case.
The Firefox hardware report was published for a while and the last activity here is 3 years old.
Closing for now.
Status: NEW → RESOLVED
Last Resolved: 2 days ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.