this post was submitted on 10 Mar 2025
47 points (98.0% liked)
Programming Circlejerk
236 readers
2 users here now
Community to talk about enlightened programming takes
Rules:
- read and follow the programming.dev code of conduct
- no flamewars
- mark your unjerks
- only programming related content allowed
- link to the original source
- do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.
founded 6 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think this is referring to clients that are actively connected and transmitting / receiving data. For example, watching a video means you need a fairly constant connection to the server. 100 concurrent users would be able to begin watching a, lets say 10 minute video. For these 10 minutes, the server may not accept a new user. After 10 minutes, slots free up that can handle other users. Technically it is more complicated than this, involving bandwidth, number of cores / threads, databases, queries, etc which will limit how many users the service can handle, and connections can be made and broken to allow the service to serve a larger number of concurrent clients.
In the above example, you have 100 users every 10 minutes which is 14,400 users a day assuming 100% utilization