Search

• Table of Contents
• Nextcloud 10 Server Administration Manual Introduction
• Nextcloud 10 Release Notes
• Installation
• Nextcloud Server Configuration
  • Warnings on Admin Page
  • Using the occ Command
  • Configuring the Activity App
  • Configuring Memory Caching
  • Defining Background Jobs
  • Config.php Parameters
  • Email Configuration
  • Linking External Sites
  • Custom Client Download Repositories
  • Knowledge Base Configuration
  • Language Configuration
  • Logging Configuration
  • Hardening and Security Guidance
  • Reverse Proxy Configuration
  • Using Third Party PHP Components
  • JavaScript and CSS Asset Management
  • Automatic Configuration Setup
  • Nextcloud Server Tuning
    • Using cron to perform background jobs
    • Enable JavaScript and CSS Asset Management
    • Caching
    • Using MariaDB/MySQL instead of SQLite
    • Using Redis-based Transactional File Locking
    • SSL / Encryption App
  • Theming
• User Management
• File Sharing and Management
• Database Configuration
• Mimetypes Management
• Maintenance
• Operations
• Issues and Troubleshooting

• « Automatic Con...
• Theming »

Nextcloud Server Tuning

Using cron to perform background jobs

See Defining Background Jobs for a description and the benefits.

Enable JavaScript and CSS Asset Management

See JavaScript and CSS Asset Management for a description and the benefits.

Caching

Caching improves performance by storing data, code, and other objects in memory. Memory cache configuration for the Nextcloud server must be installed and configured. See Configuring Memory Caching.

Using MariaDB/MySQL instead of SQLite

MySQL or MariaDB are preferred because of the performance limitations of SQLite with highly concurrent applications, like Nextcloud.

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.

Using Redis-based Transactional File Locking

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 / Encryption App

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: grep flags /proc/cpuinfo or as a summary for all cores: grep -m 1 ^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 "AES New Instructions" 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 openssl engine command. It is active by default on the supported hardware. You can check the openssl version via openssl version -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.
• If your environment runs virtualized, check the virtualization vendor for support.

• « Automatic Con...
• Theming »