ASP #include and XML Question

[Guest_imported]

I am currently developing a website aplication, which is designed with ASP code. It retrieves all the data from an XML database, using the XMLDOM to parse with ASP.

Since I am building, everything an ASP, i am tempted to breakdown the templates and create master templates using the #include method, to load the different active subsections of the page. Such as Main Navigation, Section Navigation, Header, Footer and Body.

The website will be hosted on a shared Windows 2000 server. I dont expect our website's traffic to be very high, but I am a little concerned about the system's memory requirements that this type of programming can excert on the machine.

I am not a systems engineer or a computer scientist, I am an architect who has learned programming on the way, so I understand how the program works, but not what It actually uses up, memorywise RAM, Cache ???. Since the beta testing is done only by a handful of people, I have no real feel of haw the system is going to behave once its live.

So if anybody can give me some advise or a "heads up!", I would greatly appreciate it.

Thank you,

Alvaro

 

[rac2]

My experience on one ASP web site with few concurrent users is that using templates does not affect performance noticably. The time saved in coding initially and later in making changes is very significant.

Every #INCLUDE means that another file must be loaded in order to construct the page. I don't know what features the operating system and the web server might have to eliminate the need to find these files repeatedly, but there must be something.