Bikeshed the source name for per-process

[kenchris]

The per-process support will be exposed as a new source type, but it's a bit hard finding a good name :-)

Some current ideas:

• "cpu-self"
• "cpu-same-origin"
• "cpu-same-site"

"self" is probably not so descriptive, as as processes are often shared across multiple instances of the same site/origin, something like "same-origin" or "same-site" might make more sense. Cookies seem to use the "same site" nomenclature.

@Elchi3 maybe you have some ideas given your work on MDN.

[Elchi3]

I have no concrete naming proposal but I think it would help to understand the scopes here. Would the following documentation be correct? ("cpu-thread" is my invention for illustration).

• "thermals" represents the global thermal state of the entire system.
• "cpu" represents the average pressure of the central processing unit (CPU) across all its cores. This state can be affected by other apps and sites than the observing site.
• "cpu-same-origin" represents the CPU pressure for all contexts/threads the site is using (this includes the main thread for the window and same origin iframes, and workers).
• "cpu-thread" represents the CPU pressure for an observed thread, for example a specific worker within a web application.

[kenchris]

I am a bit worried about the word thread as it is not really used in specs (to my knowledge) and APIs, though users talk about main thread. I guess it would be the JavaScript realm/context