Add a column in the comms benchmark indicating which directions use shared memory. The options are yes (i.e. purely shared-memory communication) no (i.e. purely network) and partial (= mixture of both). In practice, partial dimensions are bottlenecked by the network and thus should have the same performance as no dimensions, but it still might be nice to know.
Same information is of course also put into the json output.
Add a column in the comms benchmark indicating which directions use shared memory. The options are `yes` (i.e. purely shared-memory communication) `no` (i.e. purely network) and `partial` (= mixture of both). In practice, `partial` dimensions are bottlenecked by the network and thus should have the same performance as `no` dimensions, but it still might be nice to know.
Same information is of course also put into the json output.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Add a column in the comms benchmark indicating which directions use shared memory. The options are
yes(i.e. purely shared-memory communication)no(i.e. purely network) andpartial(= mixture of both). In practice,partialdimensions are bottlenecked by the network and thus should have the same performance asnodimensions, but it still might be nice to know.Same information is of course also put into the json output.
Thank you!