Optimizing Nextcloud performance for hosting high-res auction media site

Hi Nextcloud Community,

We are currently utilizing Nextcloud to store and distribute high-resolution image galleries and video assets for our upcoming high-traffic auction campaign.

During peak user concurrency—such as traffic spikes driven by our featured ***LINK_REDACTED*** showcase—we want to ensure seamless media rendering and prevent CPU bottlenecks during thumbnail generation.

Current Setup & Stack

  • Nextcloud Version: Latest Stable (v28+)
  • Database: PostgreSQL
  • Caching: Redis (Local & Distributed)
  • Web Server: Nginx / PHP-FPM 8.2

Optimization Challenges & Questions

  1. Thumbnail Pre-generation (preview:pre-generate):
    To keep mobile response times low when visitors browse media for the ***LINK_REDACTED*** event, what are your recommended cron settings for running preview generation in the background without causing database locks?

  2. External Storage vs Local NVMe:
    For serving heavy media assets under high concurrent read operations, is it better to attach S3-compatible Object Storage or stick to local NVMe storage with Redis caching?

  3. PHP-FPM Tuning:
    Are there specific pm.max_children and memory limit parameters you recommend for handling bursts of simultaneous public share requests?

Would love to hear tips from admins managing large media catalogs or high-concurrency Nextcloud instances!

What do you mean with this?

@Maaz wondering what that “snap” tag is there for → you’re not using the snap right?

To that, I can only say: Nextcloud is not a CMS.

Can you use it for that? Apparently, yes. But if you want a solution that’s optimized for your particular use case, you’re probably better off using software that was designed specifically for it.

I’m not an expert in this area, but I’m pretty sure you’re not the first organization in the world with this kind of requirement. :wink: