Thank you all for responses about switching from NCSA httpd to Apache web server but that is currently not an option since some of our pages are not working correctly on an Apache web server that we are using for the interim. Our site is too large and we currently don't have staff to test and do changes regardless of how minor they may be. Small changes when magnified over a large web site become a major problem. I have recommended that we do this change in the future but resources are not going to be allocated any time soon. I could understand the system having sluggish response when busy, but horrible response when only one users is on the system is a bit much. I know web sites are resource intensive, but this seems extreme. I was thinking I am currently investigating additional swap space, and other parameter tuning for web sites. Any other suggestions would be appreciated. Thanks again...
Received on Sat Feb 19 2000 - 04:35:49 NZDT