SOLVED
Are there limits to the amount of assets a folder can contain before performance is affected?
1 Accepted Solution
Correct answer by
According to this thread (https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/maximum-number-of-nodes-on...), the limitation of 1,000 children under a tree was "true" for the UI and for AEM on-premise. However, with the AEMaaCS architecture, I am not sure if this limitation still holds.
There have been several enhancements this year (2023) to the Assets UI. One of the enhancements, as far as I can recall, was specifically aimed at handling a massive quantity of assets in the UI. Unfortunately, I couldn't find the release notes. So, if you are using AEMaaCS, it might be worth trying it out. You can ask your developers to create a POC (Proof of Concept) and confirm if they notice any performance impact. If you are unable to do this on your own, I think it's fair to submit a support case to Adobe and ask directly if this limitation has been addressed in AEMaaCS.
Overall, I believe it makes sense to avoid having such a large number of assets under the same folder. Perhaps you can consider restructuring the folders in a different way, maybe using a different structure other than dates, or implementing an archiving process.
Some release notes:
Esteban Bustamante
I asked this question an adobe employe a while ago.
The answer was "at exactly 1000 assets the performance drops".
My follow up was - "How much and at which rate this gets worse?" but i could not get any more satisfying answers here.
There was no way around this... but maybe we get another answer for the current version from an adobe employee here.
We are trying to avoid having folders with more then 999 assets.
Since we moved over to AEM, folders seem to be less and less THE solution.
Not quite irrelevant, but in many cases it was impossible to rebuild the old DAM within the AEM.
Tags and other metadata became more and more the reason people find the asset they were looking for.
Instead of using the folder structure to navigate somewhere, users tend to use the search bar...
The rule i advised here at our company for additional folders is:
Please try to avoid creating additional folder structures that are already built within the tagging structure or otherwise available metadata properties.
What year an asset was purchased / created in, or which stock house it was purchased from, all of this is better put into the metadata of the assets.
Correct answer by
According to this thread (https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/maximum-number-of-nodes-on...), the limitation of 1,000 children under a tree was "true" for the UI and for AEM on-premise. However, with the AEMaaCS architecture, I am not sure if this limitation still holds.
There have been several enhancements this year (2023) to the Assets UI. One of the enhancements, as far as I can recall, was specifically aimed at handling a massive quantity of assets in the UI. Unfortunately, I couldn't find the release notes. So, if you are using AEMaaCS, it might be worth trying it out. You can ask your developers to create a POC (Proof of Concept) and confirm if they notice any performance impact. If you are unable to do this on your own, I think it's fair to submit a support case to Adobe and ask directly if this limitation has been addressed in AEMaaCS.
Overall, I believe it makes sense to avoid having such a large number of assets under the same folder. Perhaps you can consider restructuring the folders in a different way, maybe using a different structure other than dates, or implementing an archiving process.
Some release notes:
Esteban Bustamante
@dmescia2 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.
Kautuk Sahni
Related Conversations
