So I'm curious to see if anyone has tested to see how Portal performs as the number of items grow really large. A million anyone, 10 million?
- As I understand it (correct me if I'm wrong), Portal is backed by a Postgres database for storing item metadata and file items as BLOB's. So it seems to me that Portal should be able to hold a lot of items.
- Is anyone using Portal as a document management systems of sorts, i.e. storing non-spatial documents related to map features in Portal, that are tagged using a UID of whichever feature they relate to? I could envision a number of useful scenarios.
When you upload content to Portal, the physical items are stored in the content directory and information about the item is stored in the database. The database doesn't store the item itself. Are you wondering about the performance of Portal when millions of items are in the Portal?