AEM Assets: Dynamic Concurrent Upload Throttling Based on File Size

Summary 

A customer uploading 20 video files totaling 45GB (~1.8GB each) is experiencing Chrome out-of-memory crashes (Err Code 5). Potential root cause is that AEM browser-based asset upload functionality currently supports up to 7 concurrent uploads regardless of file size leading to browser memory exhaustion when uploading large files, particularly video assets.

We are requesting an enhancement to dynamically adjust the concurrent upload count based on total active file size in memory.

• Fixed concurrency of 7 does not account for file size, leading to excessive browser memory consumption with large files
• Chrome does not gracefully handle memory exhaustion in this scenario — it crashes with Err 5 rather than exiting cleanly

Proposed Solution Implement a dynamic concurrency model that uses total active upload file size as the throttling mechanism, rather than a fixed concurrent file count. The browser experience should be smart enough to do 7 for smaller files, or adjust down for larger ones.

A simple limit like 2GB total active file size would make it more robust:

• calculate total file size of the active concurrent uploads
• If total current files in progress is less than 2GB add another
• If it's above 2GB, wait for the current ones to finish before adding another up to 7 concurrent.

This approach would allow smaller files to upload in parallel at full concurrency, while automatically serializing large file uploads to prevent memory exhaustion — without requiring any user intervention.