[core] Large objects release test

[dayshah]

Why are these changes needed?

To have an ongoing benchmark that tests 4GB object broadcasts to and ingests from 9 other nodes.

Related issue number

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 added any new APIs to the API Reference. For example, if I added a
    method in Tune, I've added it in doc/source/tune/api/ under the
    corresponding .rst file.
• 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 :(

[dentiny]

Thank you! I'm also curious, when we checkin new release benchmarks, should we also attach the benchmark results somewhere (i.e. a file in the codebase so we could refer to)?

[dayshah]

Thank you! I'm also curious, when we checkin new release benchmarks, should we also attach the benchmark results somewhere (i.e. a file in the codebase so we could refer to)?

it'll automatically get made like this https://github.com/ray-project/ray/blob/master/release/perf_metrics/benchmarks/many_actors.json

https://github.com/ray-project/ray/pull/51427/files

during release process

[edoakes]

Still good practice to include results from a manual run before checking in, let's do that in all such PRs (clear paper trail when looking at git history).