[
https://issues.apache.org/jira/browse/BEAM-10542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162709#comment-17162709
]
Damian Gadomski commented on BEAM-10542:
----------------------------------------
[~tvalentyn] indeed, that increase of the metrics seem to be related to the
Jenkins migration. Especially, given that between 6/16 00:00 and 6/17 12:00 we
can notice sawtooth wave-like data. At that time we had two CI servers running
simultaneously. The upper data points seem to be always provided by the new CI,
while the bottom, by the old one.
Unfortunately, I have no idea about the actual reason behind it. The worker
nodes on the new CI are exactly the same - same processors, RAM, and disk
config. They are also created from the same disk images as the old ones. The
configuration of the jobs is also identical.
The only differences that I know are:
* the version of Jenkins server/agents - on the old CI it was a bit outdated
and we've upgraded to the newer one.
* Jenkins master connects to the workers over SSH to start the agent (on the
old CI it was JNLP from what I know)
But that, IMO, shouldn't have an impact on the tests.
> 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: P0
> Fix For: 2.23.0
>
> 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)
