Just to be clear - A single Alpha Application Server most certainly will NOT handle the stated load in the original post. Neither will a single IIS server or Apache server. No site with that kind of traffic runs on a single server of any type. You are going to require a load balanced cluster, no matter what server platform you choose.
Also as others have stated, you are talking about far more traffic than a T-1 or even T-3 could handle with a reasonable level of responsiveness.
Furthermore, if it is a business critical service, you will want some redundancy, which at a bare minimum means running the server cluster from a well-connected and dedicated Internet data center. If your business really depends on it though, this is something that should be hosted in multiple data centers in distinct geographic regions.
If this endeavor is something that you are committed to, but do not know how to architect a scalable and redundant architecture, Alpha Consulting Services can be engaged to gather requirements and design a suitable infrastructure for you.
As far as user limits and overall performance of the Application Server in general, we do not publish numbers because it is highly dependent on your hardware and Internet connection, as well as how you have built your application, so real-world number will vary greatly. As far as Steve's V10 tests, they are irrelevant in V11 because the server had been significantly enhanced and performance has been improved as a result. Some users have reported more than a 100% performance increase, but this too will vary with your specific application as well as hardware and connection.
Anyone that needs to build a multi-server cluster for a large application should contact Alpha's sales department for project-specific pricing.
User concurrency in a browser-based application is significantly different than the desktop world. During "think time" - a user looking at a screen, inputting data, reviewing a report, etc. - they are not connected to the server in any way and are not counted towards concurrent users from a load perspective. Until they click submit or take some other action that contacts the server, they consume no server resources. Only then do the connect to the server, perform some action (e.g. log in, save data, get more records, generate a report) and then immediately disconnect.
This means that 3000 logged in users is not the same as 3000 concurrent users. The concurrent user count will be just a fraction of the logged in user count, though the fraction depends highly on your specific application and its use cases.
Also as others have stated, you are talking about far more traffic than a T-1 or even T-3 could handle with a reasonable level of responsiveness.
Furthermore, if it is a business critical service, you will want some redundancy, which at a bare minimum means running the server cluster from a well-connected and dedicated Internet data center. If your business really depends on it though, this is something that should be hosted in multiple data centers in distinct geographic regions.
If this endeavor is something that you are committed to, but do not know how to architect a scalable and redundant architecture, Alpha Consulting Services can be engaged to gather requirements and design a suitable infrastructure for you.
As far as user limits and overall performance of the Application Server in general, we do not publish numbers because it is highly dependent on your hardware and Internet connection, as well as how you have built your application, so real-world number will vary greatly. As far as Steve's V10 tests, they are irrelevant in V11 because the server had been significantly enhanced and performance has been improved as a result. Some users have reported more than a 100% performance increase, but this too will vary with your specific application as well as hardware and connection.
Originally posted by Steve Wood
View Post
Originally posted by DaveM
View Post
This means that 3000 logged in users is not the same as 3000 concurrent users. The concurrent user count will be just a fraction of the logged in user count, though the fraction depends highly on your specific application and its use cases.
Comment