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

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

                Author: ASF GitHub Bot
            Created on: 07/May/22 21:24
            Start Date: 07/May/22 21:24
    Worklog Time Spent: 10m 
      Work Description: arunpandianp opened a new pull request, #17585:
URL: https://github.com/apache/beam/pull/17585

   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".
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [x] [**Choose 
reviewer(s)**](https://beam.apache.org/contribute/#make-your-change) and 
mention them in a comment (`R: @username`).
    - [x] Format the pull request title like `[BEAM-XXX] Fixes bug in 
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA 
issue, if applicable. This will automatically link the pull request to the 
issue.
    - [x] Update `CHANGES.md` with noteworthy changes.
    - [ ] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   See the [Contributor Guide](https://beam.apache.org/contribute) for more 
tips on [how to make review process 
smoother](https://beam.apache.org/contribute/#make-reviewers-job-easier).
   
   To check the build health, please visit 
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
   
   GitHub Actions Tests Status (on master branch)
   
------------------------------------------------------------------------------------------------
   [![Build python source distribution and 
wheels](https://github.com/apache/beam/workflows/Build%20python%20source%20distribution%20and%20wheels/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
   [![Python 
tests](https://github.com/apache/beam/workflows/Python%20tests/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Java 
tests](https://github.com/apache/beam/workflows/Java%20Tests/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
   
   See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more 
information about GitHub Actions CI.
   




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

            Worklog Id:     (was: 767608)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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: 10m
>  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