@AlexT,
no sir, i have in fact made sure that your suggestions were heeded. however, you persistence on the fact that every other application, module, or otherwise, anything remotely related to dolphin would be the cause of the excessive CPU resources on specific Dolphin files, is what i find to be a tad annoying. Yes you pointed out some issues you considered would help with optimization of the server, however, I can show you on dedicated servers where this problem is in existence as well.

yes see more the shared environment runs suPHP and that is the recommended configuration when running a shared or semi shared environment. changing to DSO would be particularly insane and try to run a shared environment. Your ideology is that the server should be stripped down, and that only minimal dolphin required and specific apache modules be loaded, and that this would regress the high CPU usage that the dolphin script is demanding?

Nowhere sir, is it ever specified that php should have a specific configuration, and regardless of the configuration, I think this high CPU usage will persist, but i will take your advice, and will show you that no matter what is done to a server, stripped down, nothing running but dolphin, matter of fact, i think deano has said this already, there is an extremely high CPU usage, but i will do as you suggest, and will setup an environment with minimal modules for apache, and minimal modules for php, optimize mysql, where i dont see the real gain in that, because there are a ton of queries that are reported as too large to cache, so you only get about 1/8 of the queries to cache at all.

i do believe that some of these tables can be optimized, and that there should not be queries on the SELECT * on any of the tables, you should optimize your queries, so that the database is being called for specific information that will not require extra stress and load on the CPU or the mysql server.

Regards,
DosDawg