Repository: flink-web Updated Branches: refs/heads/asf-site c2b139f18 -> 389b00e67
Fix small issues in 1.4 to 1.5 blog post Project: http://git-wip-us.apache.org/repos/asf/flink-web/repo Commit: http://git-wip-us.apache.org/repos/asf/flink-web/commit/3df7f594 Tree: http://git-wip-us.apache.org/repos/asf/flink-web/tree/3df7f594 Diff: http://git-wip-us.apache.org/repos/asf/flink-web/diff/3df7f594 Branch: refs/heads/asf-site Commit: 3df7f594ce905540e47e095704d08b34e1b89811 Parents: c2b139f Author: Aljoscha Krettek <aljoscha.kret...@gmail.com> Authored: Thu Nov 23 12:07:28 2017 +0100 Committer: Aljoscha Krettek <aljoscha.kret...@gmail.com> Committed: Thu Nov 23 12:07:28 2017 +0100 ---------------------------------------------------------------------- _posts/2017-11-21-release-1.4-and-1.5-timeline.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/flink-web/blob/3df7f594/_posts/2017-11-21-release-1.4-and-1.5-timeline.md ---------------------------------------------------------------------- diff --git a/_posts/2017-11-21-release-1.4-and-1.5-timeline.md b/_posts/2017-11-21-release-1.4-and-1.5-timeline.md index 776cc07..b6712ae 100644 --- a/_posts/2017-11-21-release-1.4-and-1.5-timeline.md +++ b/_posts/2017-11-21-release-1.4-and-1.5-timeline.md @@ -27,7 +27,7 @@ in the hands of users. This post will describe how the community plans to get there and the rationale behind the approach. -## Coming soon: Major Changes to the Flinkâs Runtime +## Coming soon: Major Changes to Flinkâs Runtime There are 3 significant improvements to the Apache Flink engine that the community has nearly completed and that will have a meaningful impact on Flinkâs operability and performance. @@ -38,9 +38,10 @@ completed and that will have a meaningful impact on Flinkâs operability and pe Next, weâll go through each of these improvements in more detail. -## Reworking Flinkâs Deployment Model and Distributed Process +## Reworking Flinkâs Deployment Model and Distributed Processing -[FLIP-6](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077) is an initiative +[FLIP-6](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077) (FLIP is short for +FLink Improvement Proposal and FLIPs are proposals for bigger changes to Flink) is an initiative thatâs been in the works for more than a year and represents a major refactor of Flinkâs deployment model and distributed process. The underlying motivation for FLIP-6 was the fact that Flink is being adopted by a wider range of developer communities--both developers coming from the big data and @@ -74,7 +75,7 @@ driven network I/O and application-level flow control, ensuring that Flink will network capacity, as well as credit-based flow control which offers more fine-grained backpressuring for improved checkpoint alignments. -In our testing ([see slide 26 here](https://www.slideshare.net/FlinkForward/flink-forward-berlin-2017-nico-kruber-building-a-network-stack-for-optimal-throughput-lowlatency-tradeoffs)), +In our testing ([see slide 26 here](https://www.slideshare.net/FlinkForward/flink-forward-berlin-2017-nico-kruber-building-a-network-stack-for-optimal-throughput-lowlatency-tradeoffs#26)), weâve seen a substantial improvement in latency using event-driven network I/O, and the community is also doing work to make sure weâre able to provide this increase in speed without a measurable throughput tradeoff.
