Server Capacity: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
 
Line 2: Line 2:
[[OSE_Server#Server_Requirements]]
[[OSE_Server#Server_Requirements]]


=Throughput=
=Throughput - and Current OSE 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
*Says 250 users per core

Latest revision as of 21:07, 23 June 2022

OSE Infrastructure

OSE_Server#Server_Requirements

Throughput - and Current OSE 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?
  • Optimal server cluster is 3 servers - [2]
  • wikipedia has 350 servers? [3]
  • Absolute max for a single server is 65k users connected, but really dependent on server specifications? How long is a connection - is it only during a database request? [4]
  • 1000 users at a time is for 4 GB RAM? [5] Does that mean that we are likely to handle 16k simultaneous users?