Ok.. Thank For all Answers.. I could not solve problem.. it goes on.. :( you did your best.. Thanks.. i think i do something wrong.. i have 5 XOOPS sites and and all have this problem.. so now i understand.. i cant solve this problem.. :( i will find an other way.. Thank for answers .. you tried to help..

Hallo again me.. Now my server says me GO AWAY.. i need a host which is with out CPU problem... can you advice a host for me?? THANKS..

For which budget?

I have the same problem on my site.
My webhost allows only 3600 CPU seconds/day, but I was using over 20000. After enabling all cache features and blocked web bots, it reduced it to 15000, which is still too much. My site recieves around 100,000 requests/day.

It's hard to pinpoint where all the CPU usage is coming from... anyone have ideas?

Quote:

Don't look too far for the answers. If you cannot change server configuration there are some steps you MUST to do:

1. Preferences -> Main "Use gzip compression?" - NO!!! NO!!! NO one more time!!!

2. Update module template .html files from themes/your theme/templates directory? - NO!!!! It reduces MySQL queries count.

3. Cache the most static blocks, forhttp://www.gdamania.net/ they coul be "Site Search" - no less than 1 day, "Welcome to GDAmania!" - no less than 1 day, "Latest Downloads" ~ 30 min, "Current Forum Topics" ~ 5 min. "Latest News" ~30 min. "Language" no less than 1 day. Of course cahching of dynamic blocks, where content depends on the site user group, is more difficult, so for beginning leave as is.

I can bet, that this would reduce load ~3-5 times onhttp://www.gdamania.net/
100 000 requests isn't very much to handle. As I can see You have Alexa ~300000, so I pretend even mediocre Celeron 1000Mhz, 1Gb RAM can host 50 XOOPS sites like this.

In my case I split the site into 2
Yet really the way I am using XOOPS is more like an operating system then just a cms.
The amount of modules I have is like having windows, I was think this morning and how if I have my own server how many calls to the database are likey, if I make the sites one again.

I have done the Gzip off as you say; as I have seen many posts saying it doesn't work; does it?

Also if we look at the xoops.org/dev/? site its self that seperated into sections.

So the work being done on improving performance of XOOPS and not its modules is a good idea, I feel now!
As the faster the opperating system can handle, the software and the more stable; the less trouble overall!