[ 
https://issues.apache.org/jira/browse/BEAM-13073?focusedWorklogId=685484&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-685484
 ]

ASF GitHub Bot logged work on BEAM-13073:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Nov/21 20:30
            Start Date: 23/Nov/21 20:30
    Worklog Time Spent: 10m 
      Work Description: tvalentyn commented on pull request #16045:
URL: https://github.com/apache/beam/pull/16045#issuecomment-977145175


   LGTM. I tested the change on #13073 and it addresses the regression 
identified by performance tests.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 685484)
    Time Spent: 1h  (was: 50m)

> Unexpected GC when using Java 11
> --------------------------------
>
>                 Key: BEAM-13073
>                 URL: https://issues.apache.org/jira/browse/BEAM-13073
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-harness
>            Reporter: Luis
>            Assignee: Kenneth Knowles
>            Priority: P1
>              Labels: java11, java9, performance
>             Fix For: 2.35.0
>
>         Attachments: perf_regression_java_11.png
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Beam SDK has been supporting Java 11 for a while (I guess the support was 
> introduced here https://issues.apache.org/jira/browse/BEAM-2530). 
> Unfortunately, in Spotify we are still experiencing performance issues when 
> using Beam SDK 2.32, Google Dataflow and Java 11.
> Thanks to [~emilyye] and [~iht], they confirmed JVM 11 is using SerialGC, 
> while Java 8 uses ParallelGC. It sounds like ParallelGC is a good option for 
> high throughput / low latency jobs. For Java11 we'd expect to use G1GC or 
> ParallelGC.
> This SO question [1] clarifies that JVM chooses SerialGC when it treats the 
> machine as a "client". It looks like the Java SDK container could benefit 
> from using `-XX:+AlwaysActAsServerClassMachine`. Is that correct?
> Let me know if the ticket needs further context or adjustment. (It is my 
> first time creating a ticket here).
>  [1] 
> [https://stackoverflow.com/questions/52474162/why-is-serialgc-chosen-over-g1gc]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to