AEM Assets performance issues when processing large CSV files
Uploading very large CSV files with millions of records in Adobe Experience Manager as a Cloud Service (AEMaaCS) – Assets can result in slow processing and delayed data access. The product supports CSV uploads without enforcing a documented row limit, but large datasets require careful handling to maintain stable performance. To resolve the issue, split large CSV files into smaller datasets before uploading.
Description description
Environment
- Product: Adobe Experience Manager as a Cloud Service (AEMaaCS) – Assets
- Scenario: Uploading and accessing large CSV files
- File type: CSV
- Instance: Production
Issue/Symptoms
- Uploading a CSV file with over 24 million records results in slow processing.
- Fetching the data from AEM Assets takes longer than expected after the upload.
- Accessing a large CSV file in DAM shows noticeable performance degradation.
Resolution resolution
There is no hard product limit on the number of rows in a CSV file uploaded to AEM DAM. If upload or access issues occur, such as slowness or errors, split the dataset into smaller files before uploading. Verify that the upload completes successfully and that the asset can be accessed in DAM without delays or errors.
Note: Storing very large datasets directly in DAM is not optimal for high‑performance validation scenarios that involve many concurrent users.