Yue wrote: ↑May 17th, 2023, 6:57 pmdo you mean switching between views of (1) physical core(s) usage(s) and (2) all logical processors or one (scrolled) view for each logical processor (because I cannot imagine you really mean that one)?
Yue wrote: ↑May 17th, 2023, 6:57 pmIs there no way to make an exception in your code just for your CPU skin
Yue wrote: ↑May 17th, 2023, 6:57 pmI don´t feel adressed by this question and I guess it wasn´t meant this way.
Yeah, I know, naming is a bit confusing / overlapping in these cases. But let's put it another way, hopefully crystal clear - in the realm of processing units this is the structure that all computers have:
1 or more physical processors -
(that each can have) ->
1 or more physical cores -
(that each can have) ->
1 or more logical cores (Windows Task Manager calls the latter logical processors, but that's just semantics, really - like you said, the key in differentiating is physical vs logical, or physical vs virtual, if you like).
Originally, my skin was designed so that at some point in the future it will be able to navigate via scrolling through multiple physical (and separate, of course) processors. However, since probably all regular users have just 1 physical processor (divided into physical cores, themselves divided into logical cores or logical processors as Task Manager calls them) and multiple physical processors are used almost exclusively in supercomputers, I thought that I should forget about scrolling through multiple physical processors (which we regular users won't buy in our lifetime anyway) and just scroll through the single physical processor and its logical cores instead.
In other words, if I would scroll through logical cores, I wouldn't display the whole list of logical core frequencies, usages and temperatures when I'm on the single / overall physical processor that we all have, but I would instead display each logical core data in its own "navigation page", if you will, according to the scrolling. For example...
- no scroll: tooltip made of logical core count, frequency, usage, temperature for the single (or overall) physical processor
- scroll once: tooltip made of current logical core number aka 1, frequency, usage, temperature for the logical core number 1
- scroll twice: tooltip made of current logical core number aka 2, frequency, usage, temperature for the logical core number 2
... and so on ...
The disadvantages, as I said, are not viewing all core data on the same page anymore, and the counter for the average and period over which the average is measured not starting until the said logical core is scrolled over. The advantages are multiple and significant, at least in terms of development and efficiency, so I'd prefer it, as the skin designer. My question was what would you prefer, as a hypothetical user? Do you think this (scrolling over logical cores this way) would be acceptable / illustrative / match expectations or user needs?
Note: In terms of code, it's not about deactivating anything. It's whether I should have 33 measures for physical processor + logical core nominal frequencies, 33 for their usages, 33 for their temperatures, 33 for their percent of nominal frequencies, 33 for their actual frequencies based on the percent and nominal frequency product, plus another 2 or 3 for computing the average and period for only the physical processor in order to avoid multiplicating them again by 33, running at all times (32 is the maximum number of logical cores I am willing to display) ... or just 1 measure of each, plus the same 2 or 3 for the average part, but for the currently "active" or "scrolled" physical processor / core (avoiding multiplicating is not needed here, but they will obviously "switch" to the said physical processor / core only on scroll).
P.S. If I scrolled through physical processors, making an exception wouldn't be needed since I would only do the average part for the physical processor, and not logical cores (adding another bunch of measures to the already many of them or the inabilty to display yet another long list of values are good reasons for that). If I scrolled through the one physical processor and its logical cores, making an exception would mean that instead of the 2 or 3 measures I mentioned above, I would need to have ((2 or 3) * 33) to monitor logical cores at all times as well. Not overkill, but the, who doesn't like a skin made of just a couple of measures?
![Confused :confused:](./images/smilies/bn.gif)