I've just found that I shouldn't really need to compile PHP because the "Build Matching PHP Binary" actually did work. The reason I thought it didn't was because I thought it was missing a few on the phpinfo() page I made showing the modules... infact it was just missing '--with-apxs2=/usr/local/apache/bin/apxs'...... obviously, because it's not apache.
I originally thought compiling php again would fix the problem I am having here:
Now this is even more puzzling because both apache's PHP and litespeed's PHP contain the same modules... so that shouldn't be a problem... What could be causing this?
I mean that it increases server load to far too high for the server to cope... takes a while to return to normal after me stopping compiling (or atleast closing the webpage with the compiling going on).
compiling will cause high CPU utilization, so server load will be definitely higher. Same is true if you rebuild Apache with easyapache. Just do that due your off-peak hour.
Yeah but I don't expect exim, ftp etc. to all go down and server load over 100? Of course it will increase server load, but apache update only increases it a little, not by 100...?
Must be something wrong the PHP binary created, you can try restart over. Put LiteSpeed on another port to make sure everything work properly, then let it take live traffic.