Max number of files in the DAM | Community
Skip to main content
Level 2
October 16, 2015
Solved

Max number of files in the DAM

  • October 16, 2015
  • 4 replies
  • 2105 views

I'm looking for some definitive guidelines on the max number of files that are allowed in the DAM.

What I've read so far seems to indicate that there may not be a maximum number overall, but there is a limit per folder.

Is that the case?

This question is specific to AEM 5.6.1

I read somewhere that the max is 300 to 400 files per folder.  That seems pretty low to me.

Anyone have insight on this?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Lokesh_Shivalingaiah

As you mentioned, there is no limit on the max number. However, we can restrict to some arbitrary number considering the performance. [1] is a good read about it

[1] https://cqdump.wordpress.com/2015/07/09/1000-nodes-per-folder-and-oak-orderable-nodes/

4 replies

Lokesh_Shivalingaiah
Lokesh_ShivalingaiahAccepted solution
Level 10
October 16, 2015

As you mentioned, there is no limit on the max number. However, we can restrict to some arbitrary number considering the performance. [1] is a good read about it

[1] https://cqdump.wordpress.com/2015/07/09/1000-nodes-per-folder-and-oak-orderable-nodes/

rbemillerAuthor
Level 2
October 16, 2015

Not sure how this got marked as solved.  

Anyway, I appreciate the feedback bsloki.  The details you shared seem to be related to AEM 6.x.  I was wondering about AEM 5.6.1.

Does anyone know if the same rules apply to 5.6.1, or are the limits (recommendations) even lower?

Thanks!

Lokesh_Shivalingaiah
Level 10
October 16, 2015

Actually not, it talks about AEM 5.6.1 itself but it does mention that with Oak in AEM 6.x, you can create much more nodes without any performance hits

Adobe Employee
October 16, 2015

Hi,

in AEM5.6.1 the recommended limit was 1000 child nodes, see the presentation here[1]. The issue comes when you modify/update a node when that node has many siblings. Having many nodes is ok for static content, not for dynamic content. i.e. content that is frequently modified.

Another thing to consider, how can someone view so many nodes/assets/pages in a single folder, it is a lot of data to go through. If you open the folder/node in CRXDE, having so many child nodes can affect the UI performance as well.

So maybe spend more time on deciding how you can bucket your assets into folders to reduce the number of assets in each folder. It will make it easier to find what you are looking for, as opposed to going through many hundreds/thousand assets. You can use the search facility to get exactly what you want, but sometimes users will browse. In AEM 6.1 you can apply meta data schemas at a folder level [2], so you really want to think carefully about your folder structure, rather than throwing everything into a single folder.

Regards,

Opkar

 

[1] http://www.connectcon.ch/content/dam/cqcon/Pr%C3%A4sentation_Marcel_Reutegger.pdf

[2] https://docs.adobe.com/docs/en/aem/6-1/administer/content/assets/metadata-schemas.html