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

Danny McCormick commented on BEAM-14437:
----------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/21575

> 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: 1h 20m
>  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