Forum Moderators: open
In my environment, day by day, number of page views increase.
The more traffic the more data-driven ASP pages become less efficient to serve client.
I reached this solution: to cache the stream in HTML and to serve it for the entire day (or week!).
Scenario:
W2k server - sql server 2k - iis 5 on the same machine.
I guess which of these is better:
1) Store HTML code as text in ntext field.
2) Store HTML code as binary in a BLOB field
3) Store only path and point to file system
Any opinion appreciated.
Best regards.
An even faster solution is to store the files in Application state. This depends on the total size of your HTML files and how much RAM you have on your server.
Although your best option if your page is only database-driven and not dynamic is to store all the files in the web root and not bother with asp at all.
Also, you should cache the files until the database is modified rather than use a set time period like a day or a wekk.
If you are using an ASP page, don't forget to set the last-modified header. This will make your site faster still for a lot of users.
Well done by the way, you're on the right track. I've seen so many people spend weeks tweaking and changing their databases trying to improve performance when most of the data could be cached easily like how you're doing it. A bit of lateral thinking can go a long way!
I have done this with a busy site, rather than separate IIS and SQL on two boxes, leave them on one and put a dual proc ISA caching server infront.
