zhijiangW opened a new pull request #10504: [FLINK-15069][benchmark] Supplement 
the pipelined shuffle compression case for benchmark
URL: https://github.com/apache/flink/pull/10504
 
 
   ## What is the purpose of the change
   
   *While reviewing the PR of introducing data compression for persistent 
storage and network shuffle, we think it is better to also cover this scenario 
in the benchmark for tracing the performance issues future.*
       
   *This PR would supplement the compression case for pipelined partition 
shuffle, and the compression cases for blocking partition would be added in 
FLINK-15070.*
   
   ## Brief change log
   
     - *Introduce `StreamNetworkCompressionThroughputBenchmark` for enabling 
the pipelined partition shuffle for streaming job.*
   
   ## Verifying this change
   
   The change is covered by `StreamNetworkCompressionThroughputBenchmarkTest`
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** 
/ don't know)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / 
JavaDocs / not documented)
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to