I'm scaling up my service (running on JabberD 1.4.2 of course ;) and am running into the expected xdb scaling problems. Further complicating the issue is that I'm using extended namespaces in my XMPP. I'd like to prove my service can handle 250K accounts.
The desired solution should be quick to implement (hours to days vs. days to weeks). Note that I fully expect to move over to an SQL solution in the long term. After looking at both xdb_file and xdb_sql, I believe a quick hack at xdb_file is the answer. Currently xdb_file puts all the user XML files in a single directory. I'd increase the fan out of the directory, changing ./spool/localhost/mike.xml to ./spool/localhost/m/mi/mike.xml Has anyone already done this? Is there a better path? Thanks, Mike _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
