Deprecated - Performance and scalability

Here is a trouble ticket exchange I had with folks at my host IXWebhosting.com.

If you want to check out the site, it is at:

http://www3.jrf.org/1/

At 10:37 A.M. I tried to reach our web site at

http://www3.jrf.org and it took 6 minutes and 23 seconds for the page to draw. This is unacceptable. Now it is better, (10:55 A.M. though still a bit slow.

This is probably a dumb question and I'm probably staring right at it, but isn't there a way to set the time limit for storing logs? I thought I saw something set to 7 days, but now I can't find it. Thanks.

A client runs a volunteer program and wants to maintain records for each volunteer. I plan to create a custom volunteer module for this purpose, nothing I haven't done before. But here's the catch. Do to some strange funder regulations they need to keep electronic/scanned versions of every document they collect and they want to store it all on the site and have it so that if you pull up a volunteers record, you can also access the scanned version of the original documents. (there records include everything from brith certificates to criminal background checks to timesheets)

Are there any reasons why it is not possible to use php's include_path configuration-option so drupal's code can be re-used for several sites (multisite possibility).

Is it only because people are to lazy or to busy to rewrite drupal so it will become possible? Or has it something to do with security reasons or so? When it's the first i'll be prepared to do it (as a matter of fact, I already did some rewriting and testing).

I'm using Drupal 4.7.3 and my major purpose of the instalation is to use news aggregator. But I see that the aggregator module is not updating feeds from new Blogger beta (http://beta-blogger.com).

I digged in to the aggregator module until I found the problem which I think it is. The function aggregator_parse_feed is not fetching the link property for the individual posts. So the database insert query fails.

So I am trying to push a drupal replacement for an existing XML-based in-house CMS solution for a pretty good sized customer. I've worked on several OSS and proprietary CMS, and really like what drupal has to offer. What I am wondering is if anyone has had any success running Drupal as it was designed on a backend server, performing static caches of the site, and deploying those to production. I think this solution is about the best I can do given the tools available. Take a look below, and let me know what you think. Thanks in advance!