Investigate client WebSocket performance
Open
1 - triaged
t:client
t:performance
t:websocket
- Dominant language
- Scala
- Stars
- 1.4k
- Forks
- 584
- Avg merge
- 14h 33m
- Merged PRs (30d)
- 24
Description
In https://discuss.lightbend.com/t/low-websocket-client-performance/6907 it was reported that there might be more `Streamed` messages than expected which will lead to bad performance because of all the stream handling collecting full messages.
Contributor guide
Research direction
Start with the linked discussion about low WebSocket client performance, then trace the client handling of Streamed messages to determine whether full messages are being collected unnecessarily. Compare the observed Streamed-message count with the expected behavior and document or verify the cause of the performance issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100