Running multiple virtual directories in IIS - any performance issues?
I need to run 8-10 instances of my application in IIS 6.0, which are identical but point to a different backend (handled via config files that will be different for each virtual directory). I want to create multiple virtual directories that point to different versions of the application, and I want to know if there is a significant performance hit for this. The server (Windows Server 2003) is a quad-core processor with 4GB of RAM, and a single install of the app barely touches the processor or memory, so it doesn't seem to be a concern. This doesn't seem to justify another server, especially since some of them will be very easy to use. Obviously, performance depends on the server and application, but are there any issues with this situation?
source to share
IIS on Windows Server 2003 is designed to handle multiple sites, so the number of sites alone is not a concern. The resource requirements of your application are much more important. Ie, How many, i / o, cpu, threads, database resources does it consume?
We have a Windows Server 2003 quad-core server that handles several hundred sites without issue. But one resource-intensive application cannot eat up an entire server without problems.
If you find that your application is cpu bound, you can put each instance in its own application pool and then limit the number of processors that each pool can use so that no instance can see any of the others.
I suggest you add a few at a time and see how it goes.
source to share
You should consider using multiple application pools. If you do this, and the processor, memory, IO and network resources of the server will be fine. Then there is no performance problem.
They can be run in the same application pool. But then add the thread pool problem to the list, because all applications will use the same thread pool, and if it is a 32 bit server. Then there is a limit for the w3wp process (about 1.5 GB).
source to share
The short answer is no, there shouldn't be any problem.
Basically, you are asking if IIS can host 8-10 sites ... of course it is possible. Perhaps you can configure it as separate websites rather than virtual directories and perhaps with separate application pools so that each instance is completely independent.
You note that these are not different applications to be used; assuming they are not all related to the same Access database, I see no problem.
source to share