include efficiency

[GIGN]

Just wonderng if anyone knows any links for ASP efficiency information.

I just need to know the optimum include number. We need to have 3-4 includes on each page to enable extensibility [I hope that is a word] and maintainability.

Is this number of includes extrememly inefficient?

<bb/>

 

[crazyboybert]

i dont know of any resource for how the number of includes effects efficiency but we regularly use pages with 5 or more includes on with no apparent decrease in efficiency. As we move towards more modular applications and sites we are using more and more includes and server.executes to allow easier maintenance of our sites. Im yet to put too many in that i have noticed any real cost in efficiency.

rob

 

[sweevo]

As you may know, any server side include files are loaded together at the start, along with the calling page. If you use includes within If... Then blocks, they are still loaded even if the conditions are not met, but the output will not be seen on screen. This can lead to inefficiency when a lot of includes are used. However, unless you're talking about a really high number and a lot of traffic, I don't think you'll notice too much. It is better to use server.execute if you're using IIS 5 though.

 

[GIGN]

Cheers guys - that makes me feel a whole lot better. I too am a big fan of component based systems - makes far less work for maintenance.

As far as the conditionals, well I use Execute or Transfer if I am using IIS5.0 - I am trying to follow the .net guidelines as closely as poss.



<bb/>