-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
-
None
When the max buffer queue is hit, any buffer being freed will cause reads to resume.
Under high traffic with big data, this will cause the limit to be hit too often, and the channel will be toggling on and off the receivesSuspendedByTooManyBuffers/reads suspended state.
Ricardo is suggesting to improve the algorithm by waiting for more than a buffer free before resuming reads when the limit is hit.
- is incorporated by
-
WFCORE-6057 Upgrade Undertow to 2.3.0.Final (CVE-2022-2764)
- Closed
-
WFCORE-5946 Upgrade Undertow to 2.2.18.Final
- Closed
- relates to
-
UNDERTOW-2066 AbstractFramedChannel.freeNotifier checks for receivesSuspendedByUser instead of receivesSuspendedTooManyBuffers
- Closed