You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by me...@apache.org on 2018/07/23 07:29:49 UTC
[beam-site] branch mergebot updated (ebe224b -> 86cc602)
This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a change to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git.
from ebe224b This closes #502
add 0d45033 Prepare repository for deployment.
new fabc1e3 [BEAM-4827] Add Nexmark dashboards to nexmark page on the website
new bc27da2 [BEAM-4827] Fix typos
new 86cc602 This closes #500
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
content/community/contact-us/index.html | 1 +
content/community/logos/index.html | 1 +
.../community/{contact-us => policies}/index.html | 50 +++++-----------------
.../community/presentation-materials/index.html | 1 +
content/community/youtube-channel/index.html | 1 +
src/documentation/sdks/nexmark.md | 45 +++++++++++++++++++
6 files changed, 59 insertions(+), 40 deletions(-)
copy content/community/{contact-us => policies}/index.html (86%)
[beam-site] 01/03: [BEAM-4827] Add Nexmark dashboards to nexmark
page on the website
Posted by me...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a commit to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git
commit fabc1e331784f2c550a8ac252eabca34ab60cf9a
Author: Etienne Chauchot <ec...@apache.org>
AuthorDate: Thu Jul 19 14:41:08 2018 +0200
[BEAM-4827] Add Nexmark dashboards to nexmark page on the website
---
src/documentation/sdks/nexmark.md | 45 +++++++++++++++++++++++++++++++++++++++
1 file changed, 45 insertions(+)
diff --git a/src/documentation/sdks/nexmark.md b/src/documentation/sdks/nexmark.md
index 8e9c6a7..be96a58 100644
--- a/src/documentation/sdks/nexmark.md
+++ b/src/documentation/sdks/nexmark.md
@@ -653,3 +653,48 @@ Submit to the cluster:
--streaming=false \
--manageResources=false \
--monitorJobs=true"
+
+## Nexmark dashboards
+Bellow dashboards are used as a CI mechanism to ensure no-regression on the Beam components. They are not supposed to be benchmark comparision of the runners or engines. Especially because:
+- Parameters of the runners are not the same
+- Nexmark is run with the runners in local (most of the time embedded) mode
+- Nexmark run on a shared machine that also run all the CI and build.
+- Runners have different support of the Beam model
+- Runners have different strengths that make comparision difficult:
+ - Some runners were designed to be batch oriented, others streaming oriented
+ - Some are designed towards sub-second latency, others support auto-scaling
+
+### Dashboards content
+At each commit on master, Nexmark suites are run and plots are created on the graphs.
+
+There are 2 kinds of dashboards:
+- one for performances (run times of the queries)
+- one for the size of the output PCollection (which should be constant)
+
+There are dashboards for these runners (others to come):
+- spark
+- flink
+- direct runner
+
+Each dashboard contains:
+- graphs in batch mode
+- graphs in streaming mode
+- graphs for the 13 queries.
+
+### Performance dashboards links
+
+[Nexmark performance direct runner](https://apache-beam-testing.appspot.com/explore?dashboard=5084698770407424)
+
+[Nexmark performance flink runner](https://apache-beam-testing.appspot.com/explore?dashboard=5699257587728384)
+
+[Nexmark performance spark runner](https://apache-beam-testing.appspot.com/explore?dashboard=5138380291571712)
+
+
+### Output size dashboards links
+
+[Nexmark output size direct runner](https://apache-beam-testing.appspot.com/explore?dashboard=5099379773931520)
+
+[Nexmark output size flink runner](https://apache-beam-testing.appspot.com/explore?dashboard=5731568492478464)
+
+[Nexmark output size spark runner](https://apache-beam-testing.appspot.com/explore?dashboard=5163657986048000)
+
[beam-site] 03/03: This closes #500
Posted by me...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a commit to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git
commit 86cc60234e3c67228fc3f7e5e7a224999bca4ff6
Merge: 0d45033 bc27da2
Author: Mergebot <me...@apache.org>
AuthorDate: Mon Jul 23 07:29:16 2018 +0000
This closes #500
src/documentation/sdks/nexmark.md | 45 +++++++++++++++++++++++++++++++++++++++
1 file changed, 45 insertions(+)
[beam-site] 02/03: [BEAM-4827] Fix typos
Posted by me...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a commit to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git
commit bc27da2aca04440d38c21b4bfeb3b8b800a0e500
Author: Etienne Chauchot <ec...@apache.org>
AuthorDate: Fri Jul 20 10:53:43 2018 +0200
[BEAM-4827] Fix typos
---
src/documentation/sdks/nexmark.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/documentation/sdks/nexmark.md b/src/documentation/sdks/nexmark.md
index be96a58..bf96803 100644
--- a/src/documentation/sdks/nexmark.md
+++ b/src/documentation/sdks/nexmark.md
@@ -655,12 +655,12 @@ Submit to the cluster:
--monitorJobs=true"
## Nexmark dashboards
-Bellow dashboards are used as a CI mechanism to ensure no-regression on the Beam components. They are not supposed to be benchmark comparision of the runners or engines. Especially because:
+Below dashboards are used as a CI mechanism to detect no-regression on the Beam components. They are not supposed to be benchmark comparision of the runners or engines. Especially because:
- Parameters of the runners are not the same
- Nexmark is run with the runners in local (most of the time embedded) mode
-- Nexmark run on a shared machine that also run all the CI and build.
+- Nexmark runs on a shared machine that also run all the CI and build.
- Runners have different support of the Beam model
-- Runners have different strengths that make comparision difficult:
+- Runners have different strengths that make comparison difficult:
- Some runners were designed to be batch oriented, others streaming oriented
- Some are designed towards sub-second latency, others support auto-scaling