Windows NT Performance Tuning for Web Server-Based Applications
- Unleash Your Web Server's True Power!
- Web Tuning Strategies
- Strategy: Optimize NT's Network Subsystem for Web-Based Workloads
- Strategy: Tune the Web Server Software Engine to Utilize All Available Server Resources
- Strategy: Tune Your Web Application to Utilize Available CPU Resources
- Strategy: Design the Disk Subsystem Layout for the Low Latency
Is your Web server running at its best? Do your users complain about slow Web performance from your intranet or Internet site? In an effort to improve the situation, have you purchased new hardware and yet still have not solved the problem? If you have any interest in getting the most out of your Web servers, then we have an article for you!
In this article, we explore how to tune your NT-based Web server for its very best performance. Here, we do not harp on such obvious information, such as that it is better to use compiled Web applications native for your Web server software engine (such as ASP or ISAPI for Iis, NAPI for Netscape, and so on) versus using a scripting language (such as Perl under CGI). Advising folks want to write their Web applications in—this is not new information, and besides that, everyone has their own development skill sets and may not be in a big hurry to change. Here we focus on what you can do to tune your Web server at the system level, which encompasses areas such as NT's use of server resources (CPU, network, disk, and memory) and the Web server software engine itself. By optimizing what you have, there is less chance that you will have to purchase additional server iron to meet your goals.