[Freedombox-discuss] prosody vs ejabberd

[Michiel de Jong]

i was responsible once for a 20-server ejabberd cluster serving 10 million
users (up to 1 million concurrent conversations). it's a bit of a learning
curve, but once you understand erlang as both a language and a server, it
has very high availability, and months of uptime without any maintenance. so
for that, ejabberd is good. the fact that erlang is hard to learn for the
sysadmin is not an argument here, because the freedombox will not have a
sysadmin. it will be switch on and forget. if it breaks, you either reset
factory settings, or buy a new one.

we chose ejabberd because it's stable and has been for years.

people might argue that erlang would be heavy on a plugserver. if you want
to support CouchApp, then you need CouchDb, meaning you will need erlang
anyway. I know CouchDb can be run on smartphones, so it can't be that bad.
also, take into account that the load on any chat server will be likely
between 0 and 1 messages per second.

i would say the best thing would be to do a benchmark. take an arm9 device,
run ejabberd on it, with a realistic maximum load of 10 household members
chatting through it simultaneously, then do the same with prosody and
compare cpu and memory usage.

On Wed, Sep 28, 2011 at 11:17 PM, Bdale Garbee <bdale at gag.com> wrote:

> I could use input from people who have *actually used* prosody and/or
> ejabberd about your experiences and the resulting pros and cons of the
> two daemons.
>
> At the moment, it appears that either could be a plausible choice for
> the foundation's reference implementation, but it's time to pick one.
>
> Bdale
>
> _______________________________________________
> Freedombox-discuss mailing list
> Freedombox-discuss at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/freedombox-discuss/attachments/20110929/f69d8512/attachment.html>