Web Portal Optimization through Limiting the Concurrent request Access on loading process

In Administrative section of the hosting server has ability to control number of connection   Like In IIS server administrative tool we go to Connections and Set maxConnections attribute value, By Default concurrent connections for web portal is 4294967295. 

The Parallel connections in a Browser max number of default simultaneous persistent connections per server/proxy:

Firefox 2: 2

Firefox 3+: 6

Opera 9.26: 4

Opera 12: 6

Safari 3: 4

Safari 5: 6

IE 7:   2

IE 8:   6

IE 10:   8

Chrome:  6

In .Net 2.0 have ability to deal with Concurrent access ,it deal max concurrent request per cpu is 12 , Limitation in 2.0 is it is not able to deal with multi-threading approach, in .Net 4.0 has ability to deal 5000 concurrent access per cpu and also have ability of multi-threading.

Now, the Concern is we want to limit the access of some module in application, In IIS 7 they have greatly optimized the performance of Web servers with multi-threading and concurrent , in previous version of IIS we have one configuration file for whole applications and pools on server that is not loosely coupled in modules , In IIS 7 and 7.5 we have ability to set the configuration file for Application Pool Wise , through this we Limit the Pool Concurrent Users only for that pool not for whole application.