Web Server Connections
I was wondering if anyone could comment on how many concurrent connections a web server device would usually have, or is there a limit?
Varies depending on the device / software, but there is almost always a limit.
The first thing you need to know is this a computer based web server or a device based web server I.E. ILON100 or ?
The second item is if it is a computer then that would depended on the software of the system. If the system is Windows XPpro, Vista Bus. or Ult., or Windows 7 bus. or Ult. then the connection it limited to 3 user at one time.
If the software is a Windows Server edition then the connection is only limit by the speed of the computer and the internet connection.
The next item is the device web server, which most have a limit of 5 user connected at one time, but will vary upon device types and speed of connection also.
Your Internet connection speed is important for display of web pages.
Where did the magical number 3 come from? If you're talking IIS (Internet Information Server), that number is 10.
Originally Posted by lontshooter
When the limit is exceeded, you get the following message:
403.9 - Too many users. The number of users who are connected to the server exceeds the connection limit that you have set. For additional information about how to change this limit, click the article number below to view the article in the Microsoft Knowledge Base:
) Error Message: Access Forbidden: Too Many Users Are Connected 403.9
NOTE: Microsoft Windows 2000 Professional and Windows XP Professional automatically impose a 10-connection limit on IIS. You cannot change this limit.
A Device Web Server. Would the standard be 5, and if so what generally limits the number. (Processing Capabilities)
It's safe to say between 5-10. For example, the security JACEs from Tridium specifically state 5 simultaneous connections on a T-SEC-201, and 10 simultaneous connections on a T-SEC-601.
Originally Posted by gnsy1
The limits can be generalized into:
* hardware (cpu speed, memory, I/O throughput) and software limits of the OS where it is running
* type of content: java applet/flash/xml/plain vanilla html;
* content origin (static or dynamic);
* content cached or not;
* amount of data on an average page
It depends on your metrics used for benchmarking. One way to find out is to have as many users connect to it until it becomes unresponsive.
Plenty of food for thought. I will investigate further.