Case study
Nextcloud slow uploads linked to Redis, database and storage pressure
Nextcloud performance problems often sit between application configuration, Redis locking, database load, PHP-FPM, storage and networking. This case study outlines how we diagnose the stack carefully before making changes.
Context
A small business was using Nextcloud for file access and collaboration. Users noticed slow uploads, occasional sync problems and inconsistent web interface performance.
The stack used Linux, NGINX, PHP-FPM, MariaDB/MySQL, Redis and external/offsite backup storage.
The problem
- Uploads were slow and sometimes appeared to stall during busy periods.
- Redis file locking and PHP-FPM behaviour needed checking because symptoms were not purely network-related.
- Database growth and server I/O pressure made normal web requests slower.
- The customer needed practical fixes without risking user files.
Our approach
- Reviewed Nextcloud logs, PHP-FPM logs, Redis connectivity, file locking configuration and background job behaviour.
- Checked database size, slow queries, table health and server resource pressure.
- Reviewed storage, upload limits, cache behaviour and backup assumptions before making changes.
- Applied low-risk tuning and produced recommendations for longer-term storage and backup reliability.
Practical outcomes
Relevant technologies and keywords
These are the main technologies, services and search terms connected to this case study.
Related services
Relevant services for similar infrastructure problems.
Want help with a similar issue?
Send the symptoms, affected service, recent changes and business impact. We will suggest the most appropriate route: emergency support, a fixed-scope technical fix, an infrastructure review or a wider project.