Can you believe that it’s been more than a decade since the release of Apache 2.4?! If you haven’t replaced Apache with Nginx, then here’s a quick guide for boosting Apache’s performance using a method that’s often overlooked. Now, before we get into that, please note that I’m not claiming that Apache is faster than… continue reading.
Can you believe that it’s been more than a decade since the release of Apache 2.4?! If you haven’t replaced Apache with Nginx, then here’s a quick guide for boosting Apache’s performance using a method that’s often overlooked. Now, before we get into that, please note that I’m not claiming that Apache is faster than… continue reading.
Thanks for the guide. I made the switch to nginx years ago. I hope others do too
Very good article. Found our use case Apache now benchmarks faster.
That is a good breakdown on how to improve performance.
For fun, I tried apache2 -M
on my Debian-based RPi-5 and got an error message about the working directory environment variable not being set. apache2ctl -M
worked though.
Thank you for sharing the article, @hydn!
Do you have a guide similar to this for Nginx? It would be incredibly helpful for the people who use Nginx.
Thanks @serhattsnmz
Yes, similar, there’s Nginx tuning tips: HTTPS/TLS - Turbocharge TTFB/Latency.
However, I wrote it back in 2018 and really need to spend some time to validate all the advice if still relevant. But for someone like yourself with good knowledge of Nginx and http(s). I think at least it should help point in some directions to have a look at.
Thank you for sharing, @hydn.
The article contains a lot of helpful tips that still seem relevant. I found it very beneficial.