This ‘happy new year’ release of ejabberd is the culmination of one year of major improvements. This is yet another milestone for ejabberd, being the starting point of a new phase of cleanup and optimisations for your favourite server.
Improvements
This release contains security fix for possible server spoofing with brute force attack on the random number generation. Even if the issue is difficult to exploit, it is recommended to upgrade your server if you’re using server-to-server (s2s) connections.
It also includes:
– better groupchat archiving support with MAM
– improved PubSub performances and control
– more shaper capabilities for listeners
– performance optimisation and lower memory consumption of the core XML processing modules
– faster core routines
Read the full announcement on ProcessOne blog: https://blog.process-one.net/ejabberd-16-01/
can you release build with
can you release build with Push notification modules
We have no idea when we will
We have no idea when we will release those module, but you can still have a look at mod_push contribution for ejabberd:
did increase ejabberd
did increase ejabberd message per second?
what is the meaning more shaper capabilities for listeners?
concurrent users per machine?
how many muc members?
nets wrote: what is the
what is the meaning more shaper capabilities for listeners?
It refers to the new option accept_interval in ejabberd_listener.
did increase ejabberd message per second?
concurrent users per machine?
This version includes optimizations in CPU and RAM consumption of core XML modules, so, it should support more concurrent users, or a higher ratio of messages proccessed per second. Exactly how those improvements benefit you, depends in your users. If you have few users that are very active, then it will reduce your CPU consumption. If you have many users with little activity, it will improve RAM consumption.
how many muc members?
There are options that allow you to limit the number of users per room, which you can set as you please. There isn't any specific limitation in ejabberd, so it depends on the user behavior and your computer capabilities. There isn't any benchmark published.
Ah, a new blog post explains
Ah, a new blog post explains other changes more relevant to your question: https://www.ejabberd.im/forum/25334/ejabberd-massive-scalability-1-node-...