Developers currently have no mechanism to obtain the memory usage of their site.
This proposal provides an API with the following properties:
- Consistent semantics across different OSes and browser vendors
- No/minimal performance overhead when not used
- Very fast to compute
This proposal relies on process-specific memory counters. It provides the most utility when the site is being hosted in a process by itself. This is an implementation detail that depends on both the browser vendor and the browsing context [e.g. # of tabs that user has open]. Despite this limitation, the API is still expected to provide utility when collected in aggregate.