Running ISPCP on a low resources system

[Cube]

1. On most systems (especially virtual servers) memory is the limiting factor. That's because we try to minimize memory usage. Stopping unnecessary services would also save CPU time. The other changes can affect the CPU negatively - but normally not very much. And the CPU is secondarily, when you don't have enough RAM.

2. I tried to shortly explain in the howto, what the changes do. For a detailed explanation of the config parameters you should read the application's manual. The changes don't do any harm, your server could run slower, less high-performance, but that's the price for a low memory usage. Each change can be easily reverted.

3. You should read the apache docs about a detailed explanation of the differences. It was also discussed here in the forum. There is no better, it depends on the case. For a "big" apache with very high traffic worker is better, faster and even less memory consuming. But the minimum worker uses is much more than prefork. So for a low memory system prefork can be better. (I hope I explained it right.)

4. What has this to do with running ispCP on a low resources system?