Re:Lessons Learned from Twenty Years of Site Reliability Eng...
by gaogao on Friday October 27, 2023 @12:47PM
(#38040808)
Also make sure your backup channel can scale. Getting a flood of 10,000+ folks over to a dinky IRC server can knock it over easy. Throttling new joinees isn't a panacea either, since there might be someone critical to get on a channel which throttling can complicate.
[ Parent
| on HN ]
Re:Lessons Learned from Twenty Years of Site Reliability Eng...
by londons_explore on Friday October 27, 2023 @01:21PM
(#38041255)
Maybe I'm naive, but I would imagine that any raspberry pi could run an IRC server with 10,000 users...
Surely 10,000 Users each on average receiving perhaps five 50 byte messages per second (that's a very busy chat room!) is a total bandwidth of 2.5 megabytes per second.
And the CPU time to shuffle messages from one TCP connection to another, or encrypt/decrypt 2.5 megabytes per second should be small.
If they're all internal/authed users, you can hopefully assume nobody is deliberately DoSing the server with millions of super long messages into busy channels too.
Re:Lessons Learned from Twenty Years of Site Reliability Eng...
by xena on Friday October 27, 2023 @04:37PM
(#38043587)
IRC servers are single threaded. You have contention at that point.
Re:Lessons Learned from Twenty Years of Site Reliability Eng...
by goalieca on Friday October 27, 2023 @07:16PM
(#38045195)
Some of the bigger irc channels have thousand users and this was in the day of 128MB of ram.