See the section Database Configuration for how to
configure Nextcloud for MySQL or MariaDB. If your installation is already running on
SQLite then it is possible to convert to MySQL or MariaDB using the steps provided
in Converting Database Type.

File locking is enabled by default, using the database locking backend. This
places a significant load on your database. See the section
Transactional File Locking for how to
configure Nextcloud to use Redis-based Transactional File Locking.

SSL (HTTPS) and file encryption/decryption can be offloaded to a processor’s
AES-NI extension. This can both speed up these operations while lowering
processing overhead. This requires a processor with the AES-NI instruction set.

Here are some examples how to check if your CPU / environment supports the
AES-NI extension:

For each CPU core present: grepflags/proc/cpuinfo or as a summary for
all cores: grep-m1^flags/proc/cpuinfo If the result contains any
aes, the extension is present.

Search eg. on the Intel web if the processor used supports the extension
Intel Processor Feature Filter You may set a filter by
"AESNewInstructions" to get a reduced result set.

For versions of openssl >= 1.0.1, AES-NI does not work via an engine and
will not show up in the opensslengine command. It is active by default
on the supported hardware. You can check the openssl version via opensslversion-a

If your processor supports AES-NI but it does not show up eg via grep or
coreinfo, it is maybe disabled in the BIOS.