Web Application Performance
Sasha Goldshtein, Dima Zurbalev, Ido Flatow · Apress eBooks · 2012
Web applications are designed to handle hundreds and even thousands of requests per second. To build such applications successfully, it is important to identify potential performance bottlenecks and to do everything you can to prevent them from occurring. But handling and preventing bottlenecks in ASP.NET applications is not confined to your code alone. From the time a web request reaches the server to the time it reaches your application’s code, it passes through an HTTP pipeline and then through the IIS pipeline, only to reach another pipeline, the ASP.NET’s pipeline, and only then does it reach your code. And when you finish handling the request, the response is sent down those pipelines until it is eventually received by the client’s machine. Every one of these pipelines is a potential bottleneck, so improving the performance of ASP.NET applications actually means improving both your code and the performance of the pipeline. These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.