AlexT,
the time you spent looking at my two servers was greatly appreciated. However, you were looking in the wrong place, because I have no other HIGH CPU usages on anything except the dolphin script. So pointing out that there are inefficient configuration settings, is 100% inaccurate. You mentioned to me that there were apache modules that can cause high load, keyword there 'can', but they are not, your statement above says 'inefficient server configuration settings that can cause high server see more load' again, keyword 'can', but they are not. The absolute of this is that Dolphin is causing the high CPU resource usage, not once are you addressing this.

Due to the fact that Dolphin is primarily insecure, and where there was a feable attempt at securing the application, that blew up in our faces and we were told to disable the security feature, that it wasnt working, and that it would be addressed at some later date. The likelihood of Dolphin becoming vulnerable to compromise is extremely high. suPHP is but one method of securing the server to protect all accounts on the server.

Item 2) you state that MYSQL was not optimized, that was on one of the servers, so that statement is incorrect and extremely inaccurate, because on the one server where MYSQL is optmized, there is the very same problem with the CPU resource usage on the XML.php file as well as the members_queries.php or whatever that file is, then there is the other /modules/boonex/index.php. Again, you address everything here but the problem, and the problem are those files.

.... 2k char limit