[GitHub] [flink] tillrohrmann commented on issue #9760: [FLINK-13982][runtime] Implement memory calculation logics

2019-10-11 Thread GitBox
tillrohrmann commented on issue #9760: [FLINK-13982][runtime] Implement memory calculation logics URL: https://github.com/apache/flink/pull/9760#issuecomment-541128765 > Thanks for the review, @tillrohrmann. > I clarified a bit on the calculation logic of shuffle memory. I think the

[GitHub] [flink] tillrohrmann commented on issue #9760: [FLINK-13982][runtime] Implement memory calculation logics

2019-10-04 Thread GitBox
tillrohrmann commented on issue #9760: [FLINK-13982][runtime] Implement memory calculation logics URL: https://github.com/apache/flink/pull/9760#issuecomment-538377296 Ok, I think you are right that producing a meaningful error message can be hard based on the linear program's solvability

[GitHub] [flink] tillrohrmann commented on issue #9760: [FLINK-13982][runtime] Implement memory calculation logics

2019-10-02 Thread GitBox
tillrohrmann commented on issue #9760: [FLINK-13982][runtime] Implement memory calculation logics URL: https://github.com/apache/flink/pull/9760#issuecomment-537483004 One way to solve the problem could be ``` final int numVariables = 8; final double[] c = new

[GitHub] [flink] tillrohrmann commented on issue #9760: [FLINK-13982][runtime] Implement memory calculation logics

2019-10-02 Thread GitBox
tillrohrmann commented on issue #9760: [FLINK-13982][runtime] Implement memory calculation logics URL: https://github.com/apache/flink/pull/9760#issuecomment-537474186 Yes, all explicitly configured values should be respected. I agree, the default values of * Framework Heap