[
https://issues.apache.org/jira/browse/BEAM-4827?focusedWorklogId=125911&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-125911
]
ASF GitHub Bot logged work on BEAM-4827:
----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jul/18 07:32
Start Date: 23/Jul/18 07:32
Worklog Time Spent: 10m
Work Description: asfgit closed pull request #500: [BEAM-4827] Add
Nexmark dashboards to nexmark page on the website
URL: https://github.com/apache/beam-site/pull/500
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/src/contribute/release-guide.md b/src/contribute/release-guide.md
index 2de1bec29..a120f0fab 100644
--- a/src/contribute/release-guide.md
+++ b/src/contribute/release-guide.md
@@ -301,7 +301,6 @@ Update
[sdks/python/apache_beam/version.py](https://github.com/apache/beam/blob/
Update Java runner specific configurations in release branch:
*
[beam/runners/google-cloud-dataflow-java/build.gradle](https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/build.gradle):
change value of 'dataflow.container_version' to
'beam-release_version_number'(e.g, 'beam-master-20180601' to 'beam-2.5.0')
-*
[beam/runners/google-cloud-dataflow-java/pom.xml](https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/pom.xml):
change value of 'version' field (e.g, '2.5.0-SNAPSHOT' to '2.5.0')
### Start a snapshot build
diff --git a/src/documentation/sdks/nexmark.md
b/src/documentation/sdks/nexmark.md
index 8e9c6a705..bf96803f2 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
+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 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 comparison 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)
+
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 125911)
Time Spent: 2h 20m (was: 2h 10m)
> Add nexmark dashboards to nexmark page
> --------------------------------------
>
> Key: BEAM-4827
> URL: https://issues.apache.org/jira/browse/BEAM-4827
> Project: Beam
> Issue Type: Improvement
> Components: website
> Reporter: Etienne Chauchot
> Assignee: Etienne Chauchot
> Priority: Major
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> To make these dashboards accessible and visible, we should publish them on
> the website as discussed on the ML.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
