404 Overhead/Performance

Results 1 to 2 of 2

Thread: 404 Overhead/Performance

  1. #1
    Join Date
    Dec 1969

    Default 404 Overhead/Performance

    Does anyone know how much overhead using the 404 error page as a directory router incurs? Right now I'm using it for rinky-dink projects in house for about 20 to 30 people but I've recently been asked if we could do it on a larger scale for a big web site. i'd hate to kill the machine with it. obviously its an extra step but how big of a step is it?

  2. #2
    Join Date
    Dec 1969

    Default RE: 404 Overhead/Performance

    depends on exactly how you&#039;re doing it, but really it&#039;s probably not so much of an overhead as to cause an enormous panic - you can probably save the overhead lost by maybe using getRows() somewhere else in place of a normal DB loop, or by otherwise optimising your code. It does incur an extra bounce back between server and client, unless you&#039;re on IIS5.0 and using Server.Transfer()<BR><BR>j<BR>http://www.atrax.ws/

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts