TerraMaster Forum

Hello TerraMaster:

In TOS 6.0.610 the load is represented as a percentage but it is not.



The CPU load is an absolute value. Maybe you can fix this.

Thank you!
Regards.

obvious wrote: ↑17 Jan 2025, 04:55 Hello TerraMaster:

In TOS 6.0.610 the load is represented as a percentage but it is not.



The CPU load is an absolute value. Maybe you can fix this.

Thank you!
Regards.

Thank you for your suggestion. I will forward this request to the product team for evaluation.

obvious wrote: ↑17 Jan 2025, 04:55 In TOS 6.0.610 the load is represented as a percentage but it is not.

The CPU load is an absolute value.

Is it really an absolute value? I think it depends on what source you read. Single core fully used == 1 ? is that what you mean? Many (many) sources will discuss cpu load in percentage terms as, it seems, this is much easier for the lay-person to understand. That gets complicated when the o/s starts reporting > 100% for multiple core cpu (today's norm). It would be nice if everyone could agree on a simplified expression. eg 100% is all cores fully utilised; 50% might be 50% of cores fully utilised or all cores to the respective amount. (But mutal agreement is highly unlikely......)

Yes, it is.

LOAD and %CPU usage are different metrics. Take this picture of my F4MAX as an example:



While rebuilding the array, CPU usage was about 15% while load was about 3. Also note that, although they look similar, they do not draw exactly the same graph.

Best regards!

Gremlin wrote: ↑18 Jan 2025, 18:38 https://en.wikipedia.org/wiki/Absolute_value

Sorry mate, at this moment I don't have time to discuss with you about that. Please google "absolute vs relative" by yourself.

Have a nice day.

I understand the meaning of "absolute versus relative," but honestly, I'm not clear on what your specific requirement is. CPU usage and system load are two different metrics. CPU usage is a single indicator, whereas system load is a composite metric that takes into account CPU usage, memory usage, disk I/O, network I/O, and other factors, and then calculates it using a weighted approach.

Don't get me wrong, my last reply was directed at Gremlin because the link about the absolute value (as modulus) have nothing to do with the topic.

I'm sure you know the difference between absolute and relative, and I don't mean to be rude either.

What I said in my first post is that the load is an absolute value but in the graph it is represented as a percentage, which I guess is an easy cosmetic issue to fix.



Best regards!

obvious wrote: ↑24 Jan 2025, 17:05 Don't get me wrong, my last reply was directed at Gremlin because the link about the absolute value (as modulus) have nothing to do with the topic.

I'm sure you know the difference between absolute and relative, and I don't mean to be rude either.

What I said in my first post is that the load is an absolute value but in the graph it is represented as a percentage, which I guess is an easy cosmetic issue to fix.



Best regards!

System load, as a composite indicator, may be more appropriately represented as a percentage.

I don't feel like continuing the discussion, but the load average is a well-known linux metric. If it has a new meaning in TOS (as a composite metric), it should be well documented so that it can be interpreted correctly.

In any case, the graph coincides with the standard one.

Kind regards.