Omeka S performance with 200.000 items

Hi Omeka S users,

We are analysing Omeka S as repository for all our digital content, but we are concerned about Omeka S performance as we have more than 200.000 items with more than 1 million of resources and we have not been able to find any Omeka S installation with more than 50.000 items.
Do you think Omeka S could have problems managing so many records?
Has anyone experience with such large repositories?
Any recommendation on how to configure our Omeka S to have no performance problems? Any useful module?

This topic was automatically closed 250 days after the last reply. New replies are no longer allowed.