I would be careful when you use a PHP Accelerator on more than 10 sites as our experience has shown is that they fail at around this point. The problem is that eZ publish creates a php file for every screen if cache is on and the accelerator promptly makes a file for that and stores it so that it does not need to be processed again. This can lead to tens of thousands of PHP cache files, which slows the whole system down.
Until we can resolve this problem we have turned them off, we have tried, Turck, APC, PHP Accelerator etc.
I would appreciate if anyone else has a method of getting around this problem.
Tony
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
Thanks for your reply too !
in fact we are about to set up our first ez publish site on that server where other php sites are hosted.
For the moment, and it is more convenient for us at the moment, we'll set up an instance of ez publish for just that website on its particular webspace (without sharing the install over multiple sites). But your answer is really helpful in the fact that it gives us information about what to do in the near future when we decide to use ez publish more often on our php developments !