Understood, but I wonder if you could not simply create an "Experimental Settings" tab with ample warnings and detailed descriptions on each setting. I've been running your software for 15 years and still don't understand some of the stuff hidden in init.php. These settings may be helpful to more people if only they could access them.

 

define( 'OUTPUT_CACHE_METHOD', 'Redis' ); // Store guest pages in Redis

Is this the best option for performance? I am using redis already for all the other cache settings available on AdminCP.

Edited January 16, 20214 yr by sobrenome

There are several factors at play so I can't say "yes" or "no" without qualifying the answer. You may wish to try it out to see if it performs the best in your case in any event.

I am using it and the website feels faster. But I have not made any speed test notes, it is just a subjective perception. Thanks!

 

define( 'OUTPUT_CACHE_METHOD', 'Redis' ); // Store guest pages in Redis
define( 'STORE_METHOD', 'Redis' ); // Use Redis for datastore
define( 'CACHE_METHOD', 'Redis' ); // Use Redis for caching
define( 'REDIS_ENABLED', true ); // Use Redis for sessions

 

can I use mysql for sessions (for other SSO integration is based on that) and Redis for everything else like this?

define( 'REDIS_ENABLED', false); // Use Redis for sessions
define( 'OUTPUT_CACHE_METHOD', 'Redis' ); // Store guest pages in Redis
define( 'STORE_METHOD', 'Redis' ); // Use Redis for datastore
define( 'CACHE_METHOD', 'Redis' ); // Use Redis for caching

Yes