-
-
Notifications
You must be signed in to change notification settings - Fork 37
Performance Tuning
github-actions[bot] edited this page Feb 8, 2026
·
2 revisions
Tips for large trees, heavy usage, and stable deployments.
- Use a dedicated uploads directory instead of mounting the root of a huge share.
- If mounting a large share, use a subfolder so scans and permission fixes are scoped.
-
SCAN_ON_START=trueis meant for first run or occasional rescan. - Keep
SCAN_ON_START=falsefor normal restarts. -
CHOWN_ON_START=trueis helpful initially; disable once perms are correct.
- Enable OPcache.
- Increase
realpath_cache_sizeandrealpath_cache_ttl. - Set
upload_max_filesizeandpost_max_size>=TOTAL_UPLOAD_SIZE. - Use
custom-php.inias a baseline (Docker already loads it); copy into your PHP conf.d and restart.
- Set
client_max_body_size 0;(Nginx) if you allow very large uploads. - Set
FR_PUBLISHED_URLto avoid URL generation issues.
Encryption at rest disables range requests and some features; this is expected and can affect perceived performance for large media.
Docs · Support · FileRise.net · Changelog
- Admin panel
- Admin gotchas
- Common env vars
- Environment variables full reference
- ACL and permissions
- ACL recipes
- Nginx setup
- Reverse proxy and subpath
- WebDAV
- WebDAV via curl
- WebDAV security and clients
- ONLYOFFICE
- Encryption at rest
- OIDC and SSO
- CIFS share auto metadata
- Sharing and public links
- Upload limits and PHP tuning
- Logs and diagnostics
- Backup and restore
- Upgrade and migration
- Migration checklist
- Maintenance scripts
- Performance quickstart
- Performance tuning
- Security hardening