Server Capacity: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 4: | Line 4: | ||
=Throughput= | =Throughput= | ||
Check out [https://developerpitstop.com/how-many-concurrent-requests-can-a-web-server-handle/#:~:text=With%20a%20single%20CPU%20core,visitors%20at%20the%20same%20time.] | Check out [https://developerpitstop.com/how-many-concurrent-requests-can-a-web-server-handle/#:~:text=With%20a%20single%20CPU%20core,visitors%20at%20the%20same%20time.] | ||
* | *Says 250 users per core | ||
*OSE is quad core - so we can handle 1000 concurrent database requests? Does that mean 1000 requests every second? | |||
*How long does a database request take? | |||
*If we can handle 1000 database requests - how many concurrent users is that? Would that make it 60k users simultaneously, because a request takes 1 second? | |||
Revision as of 20:48, 23 June 2022
OSE Infrastructure
OSE_Server#Server_Requirements
Throughput
Check out [1]
- Says 250 users per core
- OSE is quad core - so we can handle 1000 concurrent database requests? Does that mean 1000 requests every second?
- How long does a database request take?
- If we can handle 1000 database requests - how many concurrent users is that? Would that make it 60k users simultaneously, because a request takes 1 second?