Slowly making progress on XMPP

 Triviality  2 Responses »
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. Continue reading »

ejabberd cluster

 Triviality  5 Responses »
Oct 142013
 

Time to play with HA ejabberd setup now.

It was said number of daily active user will be less than 1M, and IM is just a feature of the mobile product, and believe that people will spend less then 2 hours on it everyday, also people will use the App mainly during traffic hours. So it’s 2M hours span to 7~9am and 6~8pm, 4 hours. I would like to assume it is evenly distributed, this makes the concurrent online user … 500K, Not a big number, and since it is just a non-key feature, so activities will be limited.

So I think I’d go with a full replicated ejabberd cluster, “full” means I’m going to replicate everything – password, roster, offline message. I will check the stats of the production environment to see how the resource utilization is going, and tune the allocation whenever necessary. Continue reading »