Oct 312013
 

Alright, a quick summary on XMPP before Halloween ๐Ÿ˜‰

ejabberd is up and running with 3 nodes in the cluster, and having data replicated to all 3 nodes thus service will be up and running as long as there is at least one node alive. With SleekXMPP created 5M which is much faster then ejabberdctl, created 10,000 pubsub nodes so that I can do announcement to user groups, but seems I need to recreate them as they are currently all belong to admin account, which does not fit into real world. pubsub is working as well, but I need to find another solution with better performance – it’s current about 1 subscribe/second, and seems most time was spent on authentication, so I need a feature of “subscribe for others” to speed up the test deployment, though this is not necessary in real production. I haven’t test publishing information yet.

Next step I need to do information publishing, for online and offline users, plus test how many messages I can queue, and who can do the announcement. Also, or more important, I need to test mnesia fragment which will make the cluster truly expandable. I think I’m going to create some “core” nodes to store fragmented data, and some other non-core nodes to handle connections. Once this is tested I believe everything is good for production.

I won’t do anything regarding websockets as target client will be an App, also standard for XMPP over websocket is still quite unstable thus it could waste more if I work on it more.

Pretty much everything’s here …

  2 Responses to “Slowly making progress on XMPP”

  1. Data fragmentation is still not done yet, but I’ve integrated ejabberd’s authentication with Web site (session for now, token later), also pubsub works as expected, a quick test shows that publishing to a node with 10K subscribers takes ~6 seconds. If everything is linear then this would be a good (acceptable) number since sending to 100M users will take about 17 hours. Our use case shows that the biggest subscription is ~100K.

    I haven’t play with more with information publishing yet, will focus on data fragmentation first.

  2. Damn, seems ejabberd does not play with mnesia fragmentation.

Sorry, the comment form is closed at this time.