[
https://issues.apache.org/jira/browse/BEAM-10542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165738#comment-17165738
]
Damian Gadomski commented on BEAM-10542:
----------------------------------------
Didn't know that before but the Flink, Spark and Direct Nexmark tests are
running on special Jenkins worker. The `apache-beam-jenkins-16` is labeled with
`beam-perf`, so only these tests can execute there. I'm not sure, because the
configuration on the old CI is already gone, but I guess that this worker was
configured to have only one executor (which I had missed). That would forbid
concurrent execution of the jobs and improve/stabilize the timings.
That's how I currently configured the node and seems that the timings are back
to the pre-migration values:
[http://104.154.241.245/d/ahuaA_zGz/nexmark?orgId=1&from=no:w-90d&to=now|http://104.154.241.245/d/ahuaA_zGz/nexmark?orgId=1&from=now-90d&to=now]
Dataflow was not affected because it wasn't restricted to run on
`apache-beam-jenkins-16`.
> Investigate a possible Nexmark performance regression around 06/16
> --------------------------------------------------------------------
>
> Key: BEAM-10542
> URL: https://issues.apache.org/jira/browse/BEAM-10542
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Valentyn Tymofieiev
> Priority: P2
> Attachments: image-2020-07-22-12-56-30-138.png, nexmark.png
>
>
> There is a jump in benchmark metric visible on the Dashboard:
> http://104.154.241.245/d/ahuaA_zGz/nexmark?orgId=1&from=now-90d&to=now
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
