[ 
https://issues.apache.org/jira/browse/FLINK-15145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011632#comment-17011632
 ] 

Xintong Song edited comment on FLINK-15145 at 1/15/20 9:32 AM:
---------------------------------------------------------------

I have come up with a [tuning 
report|https://docs.google.com/document/d/1-LravhQYUIkXb7rh0XnBB78vSvhp3ecLSAgsiabfVkk/edit?usp=sharing].

In summary, I would suggest the following changes.
- Change default managed memory fraction from 0.4 to 0.3.
- Change default JVM metaspace size from 128MB to 64MB.
- Change default JVM overhead min size from 128MB to 192MB.


was (Author: xintongsong):
I have come up with a [tuning 
report|https://docs.google.com/document/d/1-LravhQYUIkXb7rh0XnBB78vSvhp3ecLSAgsiabfVkk/edit?usp=sharing].

In summary, I would suggest the following changes.
- Change default managed memory fraction from 0.4 to 0.3.
- Change default JVM metaspace size from 128MB to 64MB.
- Change default JVM overhead min size from 128MB to 196MB.

> Tune default values for FLIP-49 TM memory configurations with real production 
> jobs.
> -----------------------------------------------------------------------------------
>
>                 Key: FLINK-15145
>                 URL: https://issues.apache.org/jira/browse/FLINK-15145
>             Project: Flink
>          Issue Type: Task
>          Components: Runtime / Configuration
>            Reporter: Xintong Song
>            Assignee: Xintong Song
>            Priority: Blocker
>             Fix For: 1.10.0
>
>
> In release 1.10, with FLIP-49, we introduced significant changes to the 
> TaskExecutor memory model and it's related configuration options / logics.
> Since the model and configuration logics are changed, it is reasonable that 
> we also change the default configuration values. Currently, the default 
> values are set with the gut feelings and experiences from e2e tests. It would 
> be good that we try and tune the configurations with some real production 
> jobs, of various scales if possible, before exposing the configurations in 
> the release.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to