High Cost and Concurrency Limits in WebRTC Video Service
Problem
The post showcases a WebRTC video experiment (H3 Max Director) that lets users control a real‑time video feed via JSON, but users report a steep per‑minute cost ($5/min) and a hard limit of 4096 concurrent inbound connections that triggers errors, while community voting is also hampered by bandwidth constraints.
Pain points
- High runtime cost of $5 per minute
- Concurrent connection cap of 4096 causing request failures
- Bandwidth limits degrading voting experience
Questions to verify
- Would you be willing to pay extra to increase the concurrent connection limit?
- How significant is the impact of current bandwidth constraints on the voting experience?
- Have you encountered similar cost or concurrency limits on other platforms?
Evidence
quote
it costs $5/min to run, and the minimum is 1 minute.
quote
Error proxying request to container: There are more than 4096 concurrent connections inbound to the container, surpassing the limit
quote
the upvoting will continue until bandwidth improves
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.