How many datachannels

[ClosetGeek-Git]

High, I've just been browsing geckos.io but it sounds like an awesome project, but it blurs the lines a little bit (good way) in the fact that it creates a server like node using a connection meant for a peer-to-peer context, ie the datachannel. My question is how this performs when compared to other client-server stacks? What does the ceiling look like when client count starts adding up - in other words, how quickly do you start exhausting resources when compared to Websockets or other TCP based client-server protocols?

[ClosetGeek-Git]

My specific usecase may require as many as 100 clients on a single server. Clients may send as many as 60 events per second, but for most part these are trivial and will only be broadcast in order for all clients to maintain a synchronized state where needed. However each client will need to be able to send one to five non-trivial events per second that will each require a bit of work.