Added Redis, the performance feels the same / unchanged

flemmingss · August 1, 2023, 5:28am

I am running my NextCloud 27.0.1 on UnRAID as a docker container by linuxserver.io, I also have a mariaDB container with as a database for NC.
The performance of my system is ok, but I have read that Redis should speed up tings even more.
So I tested, added a redis docker container and configured nextcloud’s configuration.php like:

  'memcache.local' => '\\OC\\Memcache\\APCu',
  'filelocking.enabled' => 'true',
  'memcache.distributed' => '\OC\Memcache\Redis',
  'memcache.locking' => '\\OC\\Memcache\\Redis',
  'redis' =>
  array (
    'host' => '10.0.24.10',
    'port' => 6381,
  ),

The thing is, my NC feels the same, not any better, not any worse. Does my config look right? is this testable?
A little log from Redis, (no activity on my NC at this time, so might reflect that)

1:M 01 Aug 2023 03:10:13.234 * Background saving terminated with success
1:M 01 Aug 2023 04:10:14.017 * 1 changes in 3600 seconds. Saving...
1:M 01 Aug 2023 04:10:14.017 * Background saving started by pid 271
271:C 01 Aug 2023 04:10:14.211 * DB saved on disk
271:C 01 Aug 2023 04:10:14.212 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB
1:M 01 Aug 2023 04:10:14.219 * Background saving terminated with success
1:M 01 Aug 2023 05:10:15.036 * 1 changes in 3600 seconds. Saving...
1:M 01 Aug 2023 05:10:15.036 * Background saving started by pid 272
272:C 01 Aug 2023 05:10:15.189 * DB saved on disk
272:C 01 Aug 2023 05:10:15.189 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB
1:M 01 Aug 2023 05:10:15.238 * Background saving terminated with success
1:M 01 Aug 2023 06:10:16.068 * 1 changes in 3600 seconds. Saving...
1:M 01 Aug 2023 06:10:16.068 * Background saving started by pid 273
273:C 01 Aug 2023 06:10:16.357 * DB saved on disk
273:C 01 Aug 2023 06:10:16.358 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB
1:M 01 Aug 2023 06:10:16.370 * Background saving terminated with success
1:M 01 Aug 2023 07:10:17.027 * 1 changes in 3600 seconds. Saving...
1:M 01 Aug 2023 07:10:17.028 * Background saving started by pid 274
274:C 01 Aug 2023 07:10:17.166 * DB saved on disk
274:C 01 Aug 2023 07:10:17.166 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB
1:M 01 Aug 2023 07:10:17.229 * Background saving terminated with success
1:M 01 Aug 2023 07:24:01.756 * 100 changes in 300 seconds. Saving...
1:M 01 Aug 2023 07:24:01.756 * Background saving started by pid 275
275:C 01 Aug 2023 07:24:01.942 * DB saved on disk
275:C 01 Aug 2023 07:24:01.943 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB
1:M 01 Aug 2023 07:24:01.959 * Background saving terminated with success

jtr · August 2, 2023, 9:02pm

Your memory caching config looks fine.

For optimizing Redis specifically you want also:

Consider using a UNIX socket if the containers are all on the same host
Using the Debian based rather than Alpine based container if you’re not already (Big performance differences: Debian (Bullseye) vs Alpine-based Redis images (Docker))

One key area Redis will show up is with transactional file locking:

https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/files_locking_transactional.html

That said, you’ll get more perceivable improvements elsewhere if you haven’t already optimized them: better drives (SSD), solid CPUs, newer PHP versions, reasonable memory, making sure log levels are reasonable and debugging is off, making sure your HTTPS server’s underlying hardware supports AES-NI acceleration (i.e. Raspberry Pi’s are horrible at HTTPS for this reason because they lack AES-NI acceleration), etc.