dongjoon-hyun opened a new pull request, #57616:
URL: https://github.com/apache/spark/pull/57616
### What changes were proposed in this pull request?
This PR renames the benchmark case label `sequential fetch` to `pipelined
fetch (1 client)` in the `File-Backed Shuffle Block Fetch` suite of
`NettyTransportBenchmark`.
### Why are the changes needed?
The label is misleading. The case fires all 100 `fetchChunk` requests at
once on a single connection and then waits for all of them to complete via a
semaphore (`fetchChunksSync`), so the client never waits for one chunk before
requesting the next. This is a pipelined fetch over one connection, not a
sequential request-response loop.
The mislabel skews the interpretation of the results. For example:
```
NIO, sequential fetch 384 386
3 0.0 3844405.1 1.0X
NIO, parallel fetch (4 clients) 209 217
9 0.0 2091358.0 1.8X
```
Read as "sequential vs parallel", the 1.8X looks like poor parallelization
efficiency. The actual comparison is "pipelined over 1 socket vs pipelined over
4 sockets", where the single pipelined connection already runs at ~4.2 GB/s.
The new label makes this clear and contrasts naturally with `parallel fetch (4
clients)`.
### Does this PR introduce _any_ user-facing change?
No.
### How was this patch tested?
Label-only change; manually reviewed.
### Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Fable 5
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
