Hi Di,
A few initial questions:
- What was the previous version you were running?
- What is the value you have set in the Items Per Page setting for the full-width treeview?
- Does your installation meet or surpass the recommended hardware minimums?
Processor: 2 vCPUs @ 2.3GHz
Memory: 7GB
Disk space (processing): 50GB at a minimum for AtoM’s core stack plus more storage would be required for supporting any substantial number of digital objects.
There are some known issues we have been attempting to address across multiple releases with the full-width treeview's behavior on large hierarchies. If you'd like to read about some of the history and known issues prior to the most recent version, there is a PDF attached to this legacy issue ticket with more context:
Note that neither of the proposed solutions in that document have been implemented - though rather than adding a setting to disable paging in the treeview (originally added to help with performance, so the site is not trying to fetch and load thousands and thousands of records at once), we instead did some testing and now allow the Items Per Page setting to be set as high as 10,000 instead. If you have more than 10,000 direct child recodds from a parent top-level record, honestly it will help your site to page after that anyway, as attempting to load any more would definitely impact performance.
In any case, I will make the Maintainers aware of this thread so they can track these kinds of reports and potentially investigate further. In the meantime, let me know about those initial questions and we can go from there.
Cheers,