Benchmarks

[ohenepee]

Being low-level, how does it fare against Gorilla WebSockets and the awesome uWebSockets... say for 1 million connections? Primarily when it comes to RAM usage.

[gonzaloserrano]

Hi, did you read https://medium.freecodecamp.org/million-websockets-and-go-cc58418460bb?

[ohenepee]

10kB per connection amounts to 10GB for 1 million connections... if my calculations are correct, that's not so light tho

[gonzaloserrano]

How many KB per connection do you think is light enough? I think 10KB is amazing for a Go program where a launching a goroutine is between 4-8KB itself.

[ohenepee]

Yes your statement is very true, when compared to the goroutine allocation.

[gobwas]

Hi @ohenepee, hi @gonzaloserrano =)
Actually, 10KB is not the limit – currently application that is being discussed in the article on medium takes 8KB per connection (with GC_PERCENT set to 75%). But, if your connection does not alive – that is, does not write any data to you and you do not write data to it, then memory allocation could appear only for storing net.Conn if you use some low-level optimizations with linux epoll (see easygo/netpoll).

Thus, it much depends on use cases and behaviour patterns of your connections. For example, if some read event occur on connection, which size of the read buffer you will use? So it also makes differences on memory consumption.

Cheers !👍
Sergey.