Ejabberd resource tests/try 7: Difference between revisions
Jump to navigation
Jump to search
(Try 7:repeat try 6 with old TLS code) |
(→Try 7: Shared roster with old TLS code: mention crash) |
||
Line 2: | Line 2: | ||
A repeat of [[Ejabberd resource tests/try 6]], using the old TLS code. |
A repeat of [[Ejabberd resource tests/try 6]], using the old TLS code. |
||
This one crashed at 700 users. |
|||
=== Memory use === |
=== Memory use === |
Latest revision as of 02:23, 21 November 2008
A repeat of Ejabberd resource tests/try 6, using the old TLS code.
This one crashed at 700 users.
Memory use
Memory use vs connections
This shows max-median-min values at stable numbers of clients (min. 3 minutes).
The numbers:
resident_mem clients minimum median maximum 50 88 92 95 100 125 131 139 150 168 171 187 200 186 192 282 250 253 264 336 300 331 334 361 350 397 414 484 400 450 480 569 450 570 579 649 500 570 583 730 550 751 758 873 600 679 785 913 650 827 873 959 700 787 905 955
Virtual memory
The virtual memory size shows a smooth increase:
CPU usage
Cumulative CPU use by the ejabberd process:
Load averages, by connections and by time: