|
|
|
|
|
by kbolino
5164 days ago
|
|
Caveat: As they say, one good test is worth a thousand expert opinions, and I'm no expert. I'm inclined to say yes, it would still have a benefit. My thoughts: - Swapping the FastCGI process back in shouldn't be any worse than loading a CGI process cold and initializing it (disk caching will probably be no help to CGI here: with so little free memory, the cache will be small or nonexistent and aggressively purged); - Once swapped in, the FastCGI process will be able to handle multiple requests in less time and less memory than it would take just to start the many CGI processes necessary to do the same work. Also, if the performance of your server is an issue, your FastCGI process should never be in a situation where it would be swapped out. You need to add more memory, and/or reduce the other loads on your server. |
|