Ace's Hardware heeft een artikeltje over webserver performance in elkaar geklust. Hier heb je een stukje over server parsed HTML:
Server-parsed HTML files consist of standard HTML markup code along with server-specific code that is interpreted by a 3rd-party handler program or the webserver itself before being transferred to the client. This is the next evolution from CGI, as it is much more efficient, and inline server-side extensions such as ASP, PHP3, or even generic server supported extensions have become incredibly popular. The intention of such extensions is to make website content more dynamic and modular, and thus, easier to maintain. Additionally, a server-parsed document promotes the thin client model, minimizing client-side load and bandwidth requirements. All of this comes at a price, however, as server-parsed documents must be interpreted by the server before being sent to the client, adding additional CPU overhead. [break] ...en database connectivity: [/break] Of course, the killer app on the Internet these days has become online databases and e-commerce. Web-enabled databases and application servers have seen the most growth lately and show the greatest promise for the future. From a performance standpoint, however, online databases (using Oracle, SQL Server, Sybase, etc.) and applications call for serious performance considerations to be made. For large sites, high volume HTTP traffic and database transactions can work against each other to either crash a server or slow it to a crawl in a very short time. In these instances, it is almost always preferable to use a dedicated back-end database server (also for security reasons) with HTTP servers acting as front-end processors.