flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [flink] wsry opened a new pull request #9850: [FLINK-14118][benchmarks]Add network throughput benchmark for data skew scenario.
Date Tue, 08 Oct 2019 03:00:49 GMT
wsry opened a new pull request #9850: [FLINK-14118][benchmarks]Add network throughput benchmark
for data skew scenario.
URL: https://github.com/apache/flink/pull/9850
 
 
   ## What is the purpose of the change
   
   The purpose of this pr is to add a network benchmark for data skew scenario in which most
of the data will go to a few channels. The added benchmark simulates the most extreme scenario
in which nearly all data goes to only one channel.
   
   
   ## Brief change log
   
     - Add DataSkewStreamNetworkThroughputBenchmark to simulate data skew scenario.
     - Add DataSkewStreamNetworkThroughputBenchmarkTest to verify the added benchmark.
   
   
   ## Verifying this change
   
   A new DataSkewStreamNetworkThroughputBenchmarkTest was added to verify the change.
   
   ## 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:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message