max-mapper / max-mapper/websocket-stream
[Question] Impact of Latency on websocket streams
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 667
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
Wondering if there is any prior research on latency here?
Considering moving the www.videomail.io server to another country which will increase latency for 90% of all my clients. Because www.videomail.io relies heavily on your websocket-stream code, I'd be better careful here. How badly will more latency impact on websocket-stream's performance? Or can this be ignored since it affects initial page load only?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source files, tests, or entry points. Start by reviewing websocket-stream's documented behavior and available performance evidence, then determine whether increased network latency affects established streams beyond initial page load; done means providing a supported explanation or documented findings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100