[ 
https://issues.apache.org/jira/browse/BEAM-10542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162374#comment-17162374
 ] 

Valentyn Tymofieiev commented on BEAM-10542:
--------------------------------------------

I do not reproduce the increase in graphs around 06/16. For example the 
graphs[1] show an increase of 300% in metrics for SparkStructuredStreaming on 
Query 1 (attached). On my local machine I get roughly the same performance:

2.22.0:
{noformat}
Configurations:
 Conf Description
 0000 query:CURRENCY_CONVERSION; numEvents:1000000; streamTimeout:60

Performance:
 Conf Runtime(sec) (Baseline) Events(/sec) (Baseline) Results (Baseline)
 0000 2.8 357653.8 920000 
==========================================================================================
{noformat}

2.23.0 
{noformat}
Configurations:
 Conf Description
 0000 query:CURRENCY_CONVERSION; numEvents:1000000; streamTimeout:60

Performance:
 Conf Runtime(sec) (Baseline) Events(/sec) (Baseline) Results (Baseline)
 0000 2.7 365497.1 920000 
==========================================================================================
{noformat}

Checked via:
{noformat}
gradlew clean; ./gradlew :sdks:java:testing:nexmark:assemble  ; ./gradlew 
:sdks:java:testing:nexmark:run -Pnexmark.runner=":runners:spark" 
-Pnexmark.args=" --runner=SparkStructuredStreamingRunner --suite=SMOKE 
--streamTimeout=60 --streaming=false --manageResources=false --monitorJobs=true 
--query=1 --numEvents=1000000"
{noformat}

On the other hand, around 06/16 we made a transition to Jenkins CI[2], so if 
Java interpreter or the VM configuration has changed, that would explain the 
difference in reading. 

[1] 
http://104.154.241.245/d/ahuaA_zGz/nexmark?orgId=1&from=now-90d&to=now&var-processingType=batch&var-ID=All&var-runner=SparkStructuredStreamingRunner
[2] 
https://lists.apache.org/thread.html/re27c47eb4a542b4145ae2e6c1c98b50cdcfe4337a91a53b1c5745731%40%3Cdev.beam.apache.org%3E

 !nexmark.png! 
 

> 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: 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)

Reply via email to