What XMPP server for GNU/Linux can you recommend (other than ejabberd and OpenFire)?

Question

linux

Actually a subject.
Why other than the ones mentioned? It's simple - ejabberd is not very convenient, it develops poorly and erlang is a little annoying. OpenFire seems to be convenient, but I will not install Java without good reasons.
I've used both and that's why I'm looking for something else.
Actually there are many different servers listed. If anyone has used it please share your experience. Only free licenses are considered.
My preferences: to see a convenient config (ala squid, asterisk, etc.), a convenient web interface is also welcome, but not to the detriment of text configs.
In terms of functionality (except for the usual ones): managing rosters, the ability to store history on the server.

Answer 1

Well, the choice is really small. There is Prosody, many people like it, but it is not without flaws. In particular, it is executed in one thread, thus, the load capacity is limited to one processor core. It does not know how to cluster - the load capacity is limited to one machine. Well, the structure of the database is unlikely to be to everyone's taste - in one table everything is piled up, and even encoded in JSON. We have ejabberd on jsmart.web.id with a peak load of about 35,000 online on one machine, there are no special complaints about it, except perhaps for memory consumption. However, it can be significantly reduced if compression (zlib) and MUC are abandoned (mod_muc eats up the lion's share of memory). MUC can be put alternative, for example, mu-conference.
In the firm, in which I worked, we solved the problem more radically - we wrote our XMPP server completely from scratch (starting from expat).

Answer 2

Do you often look at the xmpp server config? Purely logically, it should be like this: you set it up once, and you don’t touch it again ... We have OpenFire installed at the factory - everyone is happy ... some sit on Exodus, some on Miranda ... there were no problems all the time ...

Answer 3

> there are no special complaints about it, except perhaps for memory consumption.
And how many? What could be evaluated in MB / user.

Answer 4

I have been using jabberd2 for several years. But I plan to try Openfire.

Answer 5

The server is also interested in storing history on the server, if there was a client for android with the ability to synchronize history, it would be generally excellent,
but what did the author stop at?