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

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

                Author: ASF GitHub Bot
            Created on: 07/May/22 21:51
            Start Date: 07/May/22 21:51
    Worklog Time Spent: 10m 
      Work Description: arunpandianp commented on PR #17585:
URL: https://github.com/apache/beam/pull/17585#issuecomment-1120299793

   I have some trouble with my local docker setup, so couldn't build the 
containers with the gradle targets locally and test.   




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

    Worklog Id:     (was: 767618)
    Time Spent: 50m  (was: 40m)

> Raise Java Http KeepAlive Cache Size
> ------------------------------------
>
>                 Key: BEAM-14437
>                 URL: https://issues.apache.org/jira/browse/BEAM-14437
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow
>            Reporter: Arun Pandian
>            Assignee: Arun Pandian
>            Priority: P2
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Java HTTP[S]Connection's keep alive by default keeps 5 idle connections 
> alive. Dataflow user workers could make 1000s of connection to the same 
> endpoint. The HTTPS handshake overhead is significant in pipelines using 
> BigQueryIO streaming inserts and bumping up the keep alive limit reduces it. 
> The keep alive connection count can be changed by setting the JVM system 
> property "http.maxConnections". 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to