With reader fields and a million documents, forget about a single database. I've worked with a commercial product that did that and performance became a bitch at 40.000 documents.
The vendor implemented a fix, but at the cost of enormous view indexes (> 2 GB). This fix basically involves resolving all the groups in reader fields and sticking all the names into a single field. The views used by users would then be categorized by that field and users would access the view with &RestrictToCategory=<user's name>.
The problem is due to the fact that the server needs to find a sufficient number of documents the user can see before any data is returned to the user. Now imagine the poor soul who has read access to only a handful of your 1 million documents. If these are spread out all over the db, the server basically needs to scan the entire million documents before the user gets his view.
The fix mentioned above causes each document to appear many, many times in the view, once for each person who can read the doc. That's why the view index becomes so large. The 2 GB view index was in a DB with 40K docs.
With reader fields and a million documents, forget about a single database. I've worked with a commercial product that did that and performance became a bitch at 40.000 documents.
The vendor implemented a fix, but at the cost of enormous view indexes (> 2 GB). This fix basically involves resolving all the groups in reader fields and sticking all the names into a single field. The views used by users would then be categorized by that field and users would access the view with &RestrictToCategory=<user's name>.
The problem is due to the fact that the server needs to find a sufficient number of documents the user can see before any data is returned to the user. Now imagine the poor soul who has read access to only a handful of your 1 million documents. If these are spread out all over the db, the server basically needs to scan the entire million documents before the user gets his view.
The fix mentioned above causes each document to appear many, many times in the view, once for each person who can read the doc. That's why the view index becomes so large. The 2 GB view index was in a DB with 40K docs.