5
Hi harvester,
As rowdie touched on above, your XOOPS sites use of server resources is going to depend very much on two things more so than anything else;
1) What modules you have installed.
2) What you have your caching set to for both modules AND blocks.
Not all modules are created equal and some are quite ineffcient in the number of SQL queries they use, and in the way they process their data (sometimes both). In high traffic situations you REALLY want to be very careful as to what modules you do add to you site, and it is generally a VERY good idea to do some performance testing before letting them loose on your production site.
As XOOPS is a dynamic portal you also have to be ultra concious of both your module and block cache settings. Even more so when using a shared hosting service. By default, neither your modules, or your blocks will be cached, and everytime someone accesses your site all the queries and data has to be processed each time. When you utilise the caching functionality of Xoops, the output of your modules and blocks are stored in cache files, so that next time somebody accesses your site, instead of all the queries and data having to be processed again, that information is simply taken from the cache file. Having a well tuned cache setup makes a [size=xx-large]HUGE[/size] difference to site performance, and again even moreso on high traffic sites.
All this said though I am a little dubious as to how your web host has setup their server, and I have a questions for you to ask them;
(1) From the information in your post it appears that your site is being hosted on a Windows Server. Is this correct?
(2)If so, it also appears that they are using Microsoft's IIS webserver. Is this correct?
(3) If so, it also looks as if IIS is configured to run PHP in CGI mode. Is this correct?
(4) If so, then do that have it configured in fast_cgi and/or do they have any caching enabled such as Zend or Turck MMCache? Configuring IIS in this way can greatly improve efficiency.
Still, these for the most part are out of your control, so you're still probably best to first take a good hard look into optimising you sites caching setup from within Xoops.