Joseph C. Lininger wrote: >> Is it? I thought the advantage of using more blown up back-ends >> consisted in having more functionalities, not performance. > > The userdb module uses berkley db or gdbm databases for authentication. > These are good for smaller setups, less than a few hundred users.
Berkley DB is one of the most powerful storage engines around. It can "only" store up to 256 terabytes of data on a single table, if you call that "few"... http://www.oracle.com/technology/documentation/berkeley-db/db/programmer_reference/am_misc_dbsizes.html > However, as these databases get large they will decrease in performance. Logarithmically on the number of keys. It will look roughly constant to most users. > Solutions like mysql and openldap are designed to handle very large > databases, and they don't degrade nearly as badly as your database > grows. MySQL has traditionally allowed BDB as a possible storage engine. I'm not familiar with OpenLDAP, but I think it also uses BerkleyDB as a backend. In both cases, I think the performance is comparable with that of alternative settings. At any rate, access to indexed tables is orders of magnitude better than the linear access time implied by plain text files such as /etc/passwd for system users. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
