When I have worked with php based websites. I try to avoid apache prefork
as that tends to be resource hungry.
Look into apache event or worker with php-fpm. You will notice a major
difference and things will be quicker.
Prefork works on a single thread to process requests.
Where as event and w
On 8 November 2015 at 10:43, Peter Presland wrote:
> Among other things I am considering moving to the Apache event-MPM using
> php-fpm and mod_proxy_fcgi because it is claimed to half (or better)
> process memory usage and provide major cpu-related speed improvements
> over the old pre-fork-MSM
Increasing site traffic has escalated both our cpu and memory issues
such that I am constantly tweeking 'bad-bot' and other defences
against multiple concurrent connections, from single IP's, IP ranges and
in total, using both mod_security and fail2ban/firewalld rules.
The problem has prompted 2 x
