[air output] Update wording to "Logical Resource Usage".

[xwjiang2010]

Update wording to "Logical Resource Usage" and remove heap/object memory stuff.

Remove memory_debug_str on head node. Remove runner.debug_str (dangling code path and duplicated logic with what's used in tune.run - I don't think people will debug trial_runner by itself these days)

Why are these changes needed?

Related issue number

#33152

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[xwjiang2010]

bunch of rllib test failures that I don't think relevant.

[krfricke]

Code looks good, just two questions:

1. Is "Logical Resource Usage" the correct term here? I don't know what it means. What is a logical resource? Maybe "Resources used" or "Assigned resources" or so?
2. Can we make sure this is found in the documentation somewhere?

[xwjiang2010]

Code looks good, just two questions:

1. Is "Logical Resource Usage" the correct term here? I don't know what it means. What is a logical resource? Maybe "Resources used" or "Assigned resources" or so?
2. Can we make sure this is found in the documentation somewhere?

"Logical Resource" is in contrast to "Physical Resource". @scottsun94 in his user research, encountered people confused about this. Hence the emphasis on "Logical".

"Usage" is also surfaced as preference from user research cc @scottsun94
To me, it's the same as granted/used/assigned etc.

I have no preference on any of the terms (apart from "Requested" is clearly misleading) - just wants to follow design suggestions here.

Agree that we should make sure that our terminology is consistent. @scottsun94 do you know where ray doc uses those terms?

[xwjiang2010]

Actually @krfricke I found it here!
https://docs.ray.io/en/latest/ray-core/scheduling/resources.html#physical-resources-and-logical-resources

So seems a valid terminology to me!

[scottsun94]

In Ray core, we already have a dedicated "Resource" doc page and talk about the difference between "logical resource" and "physical resource"

The gap I found is that people using AIR don't really understand the distinction between logical resources and physical hardware utilization. For example, in my chat with relatively new ray users like @woshiyyya, they don't really know that "resource" refers to the logical resource concept purely for scheduling.

In the long term, we probably need to introduce the "ray resource" or "logical resource" concept into AIR's doc because people shouldn't have to look at ray core doc to use AIR.

I'm fine with going with "Resource usage" for now, being a bit ambiguous before we add the related doc into AIR.

@richardliaw Any thoughts here on how we could better fill the gap?

[krfricke]

Logical resource usage is fine with me if we consistently use this term and users understand it.