[
https://issues.apache.org/jira/browse/HTTPCORE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732477#comment-17732477
]
ASF subversion and git services commented on HTTPCORE-751:
----------------------------------------------------------
Commit 3ab9d95da1a828da32246facd03aec44f30a7201 in httpcomponents-core's branch
refs/heads/master from Oleg Kalnichevski
[ https://gitbox.apache.org/repos/asf?p=httpcomponents-core.git;h=3ab9d95da ]
HTTPCORE-751: H2 protocol handler always resizes the output frame buffer to the
remove MAX_FRAME_SIZE instead of doing so only then the remote MAX_FRAME_SIZE
is lesser than the current MAX_FRAME_SIZE (partially reverts HTTPCORE-707)
> Memory Consumption and GC Performance Issues with HttpClient-5.2.1 in HTTP/2
> Communication
> ------------------------------------------------------------------------------------------
>
> Key: HTTPCORE-751
> URL: https://issues.apache.org/jira/browse/HTTPCORE-751
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore
> Affects Versions: 5.2.1
> Reporter: Sandeep_gaur
> Priority: Blocker
> Fix For: 5.2.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> After upgrading from version 5.1 to 5.2.1 of the HttpClient library for
> HTTP/2 communication, we encountered an issue. When connecting to any
> endpoint exposed by ALB (Application Load Balancer), our application consumes
> a significant amount of memory and fails to release it efficiently, leading
> to increased time spent on garbage collection (GC).
>
> Some analysis already done:-
> This is what happens: both endpoints, the client and server, transmit their
> settings approximately at about the same time. The client states it can
> handle 64K frames at max, whereas the server states it can handle 16MB
> frames. The client ACKs the server settings because its MAX_FRAME_SIZE is
> lesser than that of the server. The server, however, just ACKs the client
> settings without re-sending its settings with a smaller MAX_FRAME_SIZE. I
> suppose what means is the server acknowledges the client settings including
> the limit and states its intent to respect it and the client can be
> reasonably sure it will never get hit with a frame greater than 64K, but I
> have to got to revisit the HTTP/2 specification to be sure.
>
> For more details please follow below link:
> https://stackoverflow.com/questions/76439023/memory-consumption-and-gc-performance-issues-with-httpclient-5-2-1-in-http-2-com
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
