redis is already apart of Cloudron

Yes & no,
Yes is part of the cloudron addon, but it can be integrated in different way.

• You can use it for dynamic cache (as cloudron use in there apps), behind the php, db lvl.

• You can use it as a Full Page Cache (similar to what Cache Enebler do but in RAM and not in local disc). php lvl

• You can use it for partial page caching, in this case is at webserver/proxy lvl.

Redis is just a "database" in RAM, you can use it to store what you want, Redis is not a cache, but you can use it as it was one.

@moocloud_matt said in Apache, OLS and Nginx-Custom Benchmarks:

prestashop php-fpm + cache
We are working on prestashop for cloudron too.
This is a test to see how much flexible is our FPM+fastcgi cache setup
(No redis cache possibile, due to license on plugin to support it)

But a tweek for closed source plugin in WP.
GPL in WP is applied to ALL folder inside the ROOT folder of WP.

That mean that all function that call script in other section of the server are not included, an exemple is the ESI part for LS cache for wordpress, is the module that manage the "Edge Side Includes" feature inside WP and WooCommerce.

@lonk
it's only mandatory to be on wp.org repo

Looks like if it's a Wordpress plugin, then the code automatically falls under GLP no matter the repo: https://kinsta.com/learn/wordpress-gpl/ - that's why Wordpress premium plugins can be distributed freely.

But a plugin can implement license protections to protect their code technically, it still doesn't take away the right of the user to use it in any way they see fit EXCEPT for graphic assets.

No redis cache possibile, due to license on plugin to support it

What kind of plugin, WP is mandatorily GPL for all themes and plugin code.

We have disable the WAF features for now, that we had plan due to instability in TTFB timings.

Maybe we will add a CDN to host blacklists and information repository that WAF module need to work.
Because now it take from .9 to 2 seconds to check the ip/browser and our objective is to have mostly all normal page load in 3 or less seconds.

update on redis full Page cache (fpc)

We are working on the partial page cache, or sr-cache module.
But we are not shore if this will improve performance even more.
Is just a better management of the cache.

WordPress nginx helper

We are using nginx-helper plugin to let you clear your cache from WordPress, but due to how we are implementing stuff, we will create a fork to better sweet our nginx stack.

prestashop php-fpm + cache

We are working on prestashop for cloudron too.
This is a test to see how much flexible is our FPM+fastcgi cache setup

(No redis cache possibile, due to license on plugin to support it)

@lonk
we pause the OLS development, (is in beta and is stable) to focus on Nginx Setup.
Now our focus is to create a open beta soon, then post those app on the Cloudron store.
and early next year make a some image intercompatible, so you can change from FastCGI + PageSpeed to only FastCGI, or From RedisFPC to FastCGI, ...

But we don't know for now what we will able to do, we are focusing to prepare open beta for now.

I would love to be part of the Open Beta since I don't use my Cloudron for anything production, just dev.

But we don't know for now what we will able to do, we are focusing to prepare open beta for now.

Curious, did you ever test an OLS implementation with their official OLS Caching plugin? The subject implied you were going to but maybe I misinterpreted the acronym (Open Lightspeed?).

• https://swanson.co.uk/
• https://status.swanson.co.uk/

Something like 200 plugins, including Woocommerce.

We use WP Super Cache for fragment caching, and happy to recommend it. Although, caching is the number one cause of issues with relatively new WP devs, so I always recommend optimising the app without any caching first, especially slow queries and php warnings before getting involved with caching.

The blessing and curse of WP plugins eh, anyone can publish them

Nice work!

Ty!

@marcusquinn said in Apache, OLS and Nginx-Custom Benchmarks:

uncached benchmark

Yes we have already done it, we have a 20% on the complete page (whit all the css, js, pics, ...) tanks to the better resources management by Nginx on static content, we will provide more details later this week.
But no big improvement on just php-fpm (nignx) or fastcgi (apache) performance, apache is pretty much the best in just php content.

@marcusquinn said in Apache, OLS and Nginx-Custom Benchmarks:

Woocommerce

WC will be supported just on the Redis Full-Page Cache (Redis FPC) cache for now, we plan to support it on fastcgi early next year, with the support for tmpfs on Cloudron APP.

Btw on Redis FPC we will support partial cache soon, so wp-admin will be cached to, but partially.

Apache and Redis caching

Sorry i was not so clear on this.
Cloudron now don't provide any webserver cache (for what i know), what you have now is a DB cache, it sit between PHP and the DB.

What you see as "Apache" in the test is the standard cloudron app with "REDIS OBJECT CACHING", during the test in all app testes that lvl of cache was active, but in the Redis Full-Page Cache we use a integration between Nginx and Redis directly in addition to the Object Cache, so that PHP will never get involve if the page was already been serve to a similar client.

i will use this pics by runcloud to show you:

What we build is similar to what runcloud call RunCache, redis in this case is used to store HTML, CSS and JS content and not query to the DB.

Ultimately, we settled on FastCGI as relatively simpler and low to no maintenance needs when we're deploying updates throughout each day that need cache-clearing every time anyway.

Do you plan on having uncached benchmark instance comparisons?

For anyone else following and unfamiliar; WP Admin, Woocommerce, logged-in users, and any other dynamic content plugins can't use full-page caching.

The simplest page to test for uncached server config performance is /my-account/ when you have Woocommerce installed and /wp-login.php if you don't.

If anyone wants to test any page's uncached performance, just add a cache-busting random GET var to the end of the URL, eg: ?v=762138 and just change the number each time so it's always serves from php.

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.