You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by al...@apache.org on 2017/11/23 11:08:37 UTC
[2/2] flink-web git commit: Rebuild website
Rebuild website
Project: http://git-wip-us.apache.org/repos/asf/flink-web/repo
Commit: http://git-wip-us.apache.org/repos/asf/flink-web/commit/389b00e6
Tree: http://git-wip-us.apache.org/repos/asf/flink-web/tree/389b00e6
Diff: http://git-wip-us.apache.org/repos/asf/flink-web/diff/389b00e6
Branch: refs/heads/asf-site
Commit: 389b00e6779a24404f88707a7c4048546087039d
Parents: 3df7f59
Author: Aljoscha Krettek <al...@gmail.com>
Authored: Thu Nov 23 12:08:13 2017 +0100
Committer: Aljoscha Krettek <al...@gmail.com>
Committed: Thu Nov 23 12:08:13 2017 +0100
----------------------------------------------------------------------
content/blog/feed.xml | 9 +++++----
content/news/2017/11/22/release-1.4-and-1.5-timeline.html | 9 +++++----
2 files changed, 10 insertions(+), 8 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/flink-web/blob/389b00e6/content/blog/feed.xml
----------------------------------------------------------------------
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index f39fda1..b60a59d 100644
--- a/content/blog/feed.xml
+++ b/content/blog/feed.xml
@@ -20,7 +20,7 @@ in the hands of users.</p>
<p>This post will describe how the community plans to get there and the rationale behind the approach.</p>
-<h2 id="coming-soon-major-changes-to-the-flinks-runtime">Coming soon: Major Changes to the Flink’s Runtime</h2>
+<h2 id="coming-soon-major-changes-to-flinks-runtime">Coming soon: Major Changes to Flink’s Runtime</h2>
<p>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.</p>
@@ -33,9 +33,10 @@ completed and that will have a meaningful impact on Flink’s operability and pe
<p>Next, we’ll go through each of these improvements in more detail.</p>
-<h2 id="reworking-flinks-deployment-model-and-distributed-process">Reworking Flink’s Deployment Model and Distributed Process</h2>
+<h2 id="reworking-flinks-deployment-model-and-distributed-processing">Reworking Flink’s Deployment Model and Distributed Processing</h2>
-<p><a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077">FLIP-6</a> is an initiative
+<p><a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077">FLIP-6</a> (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
@@ -71,7 +72,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.</p>
-<p>In our testing (<a href="https://www.slideshare.net/FlinkForward/flink-forward-berlin-2017-nico-kruber-building-a-network-stack-for-optimal-throughput-lowlatency-tradeoffs">see slide 26 here</a>),
+<p>In our testing (<a href="https://www.slideshare.net/FlinkForward/flink-forward-berlin-2017-nico-kruber-building-a-network-stack-for-optimal-throughput-lowlatency-tradeoffs#26">see slide 26 here</a>),
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.</p>
http://git-wip-us.apache.org/repos/asf/flink-web/blob/389b00e6/content/news/2017/11/22/release-1.4-and-1.5-timeline.html
----------------------------------------------------------------------
diff --git a/content/news/2017/11/22/release-1.4-and-1.5-timeline.html b/content/news/2017/11/22/release-1.4-and-1.5-timeline.html
index 8079574..8c2eda9 100644
--- a/content/news/2017/11/22/release-1.4-and-1.5-timeline.html
+++ b/content/news/2017/11/22/release-1.4-and-1.5-timeline.html
@@ -153,7 +153,7 @@ in the hands of users.</p>
<p>This post will describe how the community plans to get there and the rationale behind the approach.</p>
-<h2 id="coming-soon-major-changes-to-the-flinks-runtime">Coming soon: Major Changes to the Flink’s Runtime</h2>
+<h2 id="coming-soon-major-changes-to-flinks-runtime">Coming soon: Major Changes to Flink’s Runtime</h2>
<p>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.</p>
@@ -166,9 +166,10 @@ completed and that will have a meaningful impact on Flink’s operability and pe
<p>Next, we’ll go through each of these improvements in more detail.</p>
-<h2 id="reworking-flinks-deployment-model-and-distributed-process">Reworking Flink’s Deployment Model and Distributed Process</h2>
+<h2 id="reworking-flinks-deployment-model-and-distributed-processing">Reworking Flink’s Deployment Model and Distributed Processing</h2>
-<p><a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077">FLIP-6</a> is an initiative
+<p><a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077">FLIP-6</a> (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
@@ -204,7 +205,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.</p>
-<p>In our testing (<a href="https://www.slideshare.net/FlinkForward/flink-forward-berlin-2017-nico-kruber-building-a-network-stack-for-optimal-throughput-lowlatency-tradeoffs">see slide 26 here</a>),
+<p>In our testing (<a href="https://www.slideshare.net/FlinkForward/flink-forward-berlin-2017-nico-kruber-building-a-network-stack-for-optimal-throughput-lowlatency-tradeoffs#26">see slide 26 here</a>),
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.</p>