Soo here we are with some data, and information.
To best test which solution was the best we actually have to create 3 image for nginx.
- FastCGI Cache
- Redis Full Pace Cache
- Cache Enabler (html file cache) this is here to show app level cache, with direct integration with the webserver, the call is not pass to FPM.
Our main image will be Redis Full Page Cache in till the support for RAM disk inside the container, then we will see how FastCGI will perform.
Basic information.
All the test are on our cloud platform hosted in 2 datacenter using 2 different server.
Server 1:
- 2 vCPU Intel XEON
- 2GB RAM
- and NVMe SSD on M2 Slot (over chipset) on RAID 1
Server 2:
- 2 vCPU AMD Epyc
- 2GB RAM
- and NVMe SSD on PCI-E directly to CPU on RAID 1
Both server have 1Gbit's port
The test are been done using as a client a server in the same rack, with the same specks of the tested one.
Only the app what we was testing was on at that time, and have 1 Cloudron GB as memory limit, that mean 1/2 is ram 1/2 is swap.
CPU Shares are set as default at 50%
How we test
Remember: this a preliminary test, not completely validated, we need to have various confirmation and runs before calming that they are perfect score.
We reboot the server, then stop all the app.
Check using HTOP if there was something going on on the server, if it was all clear we start testing.
We build 2 page, using divi builder the most commune builder with Elementor.


They have inline CSS, JS and we didn't use any plugin for optimizing the content, we have only use the plugin needed to enable cache control from WP.
Both pages have varius CSS file and Image + SVG.
For this test all image was the original, we will testing our auto optimize image script later.
We execute 8 test for every App.
- 5, 20, 50, 100 Concurrent session for a total of 500 session each.
- For both pages + some image and CSS in the page, not all the content
Results

What we see is 2 image that have server side cache boost there performance, they use different technique, redis full page cache save (similar to what nginx proxy cache do) a copy of the output in the RAM using the 300MB standard container provided by cloudron (we have better performance on Epyc due to low latency memory supported).
FastCGI save part of the page and the information pre-elaborate on the NVMe Storage and some on the RAM (we have a 3% better performance on the Epyc server probably due to the Storage been connected directly to the CPU).
What we didn't aspect was the terrible results (compare to the other NGINX set up) that Cache Enabler image have done, this is probably due to a check and the redirect of the request to an HTML page, saved in the NVMe Storage.
Why Redis Full Cache is for now the fastest?
Because it use a direct connection to Redis and is all in the cache, nginx don't need to interact with the FileSystem, and as we probably know Redis is one of the fastest "DB" available and is not limited to the IO for your disk, DRAM of your SSD, Chipset or raid card, but only from your RAM and CPU_RAM connection.
Especially with near AMD CPU that provider higher RAM frequency and bandwidth, Redis Full Cache page show to be the fastest solution that we can provide on cloudron.
Remember: this a preliminary test, not completely validated, we need to have various confirmation and runs before calming that they are perfect score.