![]() This is the standard open source version that is widely available and widely used across the world. Regarding ejabberd software itself, the test was made with ejabberd Community Server version 16.01. ejabberd was running on a single node of instance type m4.10xlarge (40 vCPU, 160 GiB). We used a single large instance to generate the load.īoth ejabberd and the test platform were running on Amazon EC2 instances. In that situation, the scenario produced 550 connections/second and thus 550 logins per second.ĭatabase for authentication and roster storage was MySQL, running on the same node as ejabberd.įor the benchmark itself, we used Tsung, a tool dedicated to generating large loads to test servers performance. It means that presence packets were broadcast for those users, so there was some traffic as an addition to packets handling users connections and managing sessions. The scenario involves 2.2M registered users, so almost all contacts are online at the peak load. Here is our benchmark scenario: Target was to reach 2,000,000 concurrent users, each with 18 contacts on the roster and a session lasting around 1h. Looking for experts to deploy an enterprise-grade ejabberd cluster? It turns out you can get very far with ejabberd. ![]() That’s how we ended up with the challenge of fitting a very large number of concurrent users on a single ejabberd node. However, we wanted to provide benchmark results and hard figures to demonstrate our outstanding performance level and give a baseline about what to expect in simple cases. From our experience, we all get the idea that ejabberd has massive scalability.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |