Hey everybody,
we use includes on our pages(we host several dozen sites and use includes for all the separate headers, footers etc...) at work and it looks like it is giving our server a lot of problems. The server memory keeps building up without releasing, until eventually (if the server doesn't get re-started) crashing.
We figured the abundance of includes causing the servers to parse through all the ASP pageswas the culprit, so I removed all the includes, the problem ceased and desisted. However, without the includes in there, there is a whole lot of extra (and unnecessary) coding involved.
I was just wondering if anybody had ever encountered the same problem with using includes, and if so, is there another solution as opposed to hardcoding everything. I read somewhere that using "Server.Execute" works better than includes as it loads the page into memory once and then caches it.
Any input or suggestions would be very helpful and appreciated...
Sergiogob
we use includes on our pages(we host several dozen sites and use includes for all the separate headers, footers etc...) at work and it looks like it is giving our server a lot of problems. The server memory keeps building up without releasing, until eventually (if the server doesn't get re-started) crashing.
We figured the abundance of includes causing the servers to parse through all the ASP pageswas the culprit, so I removed all the includes, the problem ceased and desisted. However, without the includes in there, there is a whole lot of extra (and unnecessary) coding involved.
I was just wondering if anybody had ever encountered the same problem with using includes, and if so, is there another solution as opposed to hardcoding everything. I read somewhere that using "Server.Execute" works better than includes as it loads the page into memory once and then caches it.
Any input or suggestions would be very helpful and appreciated...
Sergiogob