I think the situation you describe should be fine. Each user is represented by a document in the Security database - and the same for each role. If you expect more than about 8M documents of either type, I would attach a second forest to the security database. In the past, I've set up systems with hundreds of thousands of roles.
Note that the admin UI doesn't paginate users or roles. So you may find the admin UI a little tedious to use with millions of them. You may want to plan on building a simple UI of your own for that, using the security API. -- Mike On 14 Jul 2011, at 10:13 , seme...@hotmail.com wrote: > Is there a theoretical or practical limit on the number of users or roles > there are in the system? As number of users increases, how should the number > of Enodes and Dnodes be adjusted, all other things being equal? The system > can support millions or documents; can it support millions of users? Same > questions for roles. > > I understand that the number of roles and permissions on a document can > affect performance, but what about just the existence of a large number of > roles in the DB, but each doc only having a few permissions each? > > Thanks, > Ryan > _______________________________________________ > General mailing list > General@developer.marklogic.com > http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list General@developer.marklogic.com http://developer.marklogic.com/mailman/listinfo/general
