143 karma · joined October 5, 2015
We built something similar at Mattermost, which (funnily enough) is a comparable application.
https://github.com/mattermost/mattermost-load-test-ng
https://mattermost.com/blog/improving-performance-through-lo...
> Isn't really just choosing which way to throw money at the problem? Hardware costs, vs. person-hours to maintain a thin client version?
That's fair, although the second option has (in my opinion) a better return on investment given by the knowledge and experience gain.
Having built a load-test tool as well, I can say making it realistic enough and keeping it that way is possibly the hardest challenge. Maintenance cost is high, especially in a features focused environment.
Emscripten/WebAssembly actually worked rather well with audio (OPUS is just awesome) but when it comes to video it's just unfeasible, especially if you are looking at doing low latency streaming. That said, I cannot fail to mention the incredible effort done by ogv.js [1] to make a/v decoding possible almost anywhere.
Looking forward to experiment with this new API.
[1] https://mattermost.com/blog/improving-performance-through-lo...
[2] https://k6.io/