gaoyunhaii opened a new pull request #11421: [FLINK-15962][network] Reduce the 
default chunk size to 4M in netty stack
URL: https://github.com/apache/flink/pull/11421
 
 
   ## What is the purpose of the change
   
   Decrease the default Netty chunk size from 16MB to 4MB. Since Netty 
allocates memory by chunks, a smaller chunk size would decrease the amount of 
unused direct memory, thus decrease the total direct memory required.
   
   To allow users changes the default behaviors, we also makes the `page size` 
and `max order` properties of `NettyBufferPool` configurable.
   
   ## Brief change log
   
   - ce674a7530f5a1dae64aa226148a92ad58b2be76 introduce the configuration 
options and change the default chunk size to 4MB.
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
   - Unit tests for the configuration checking logic.
   - Decrease the required direct memory in E2E test 
`NettyShuffleMemoryControlTest` from 20M to 7M and verifies the test are still 
past: [Running 
Result](https://travis-ci.org/github/gaoyunhaii/flink/builds/663139174). 
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): **no**
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: **no**
     - The serializers: **no**
     - The runtime per-record code paths (performance sensitive): **no**
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: **no**
     - The S3 file system connector:**no**
   
   ## Documentation
   
     - Does this pull request introduce a new feature? **no**
    - If yes, how is the feature documented? **not applicable**
   

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

Reply via email to