Ejabberd resource tests/try 6

Try 6: Shared roster with new TLS code

This is much the same test as Ejabberd resource tests/try 5, but without manual interactivity testing and a slightly longer gap between jumps in the number of clients. It was conducted by running

 ./multihype 15 1000 50 30 

using [this test script]. That means that 50 clients would connect to the server every 1000 seconds, and continue to use it every 30 seconds until there were (15 * 50) 750 connected.

Memory use

Here you can see the memory use is slightly over 1 MB per user, and growth is approximately linear or slightly in excess thereof. The server has 1GB of ram.

Memory use vs connections

This shows max-median-min values at stable numbers of clients (min. 3 minutes).

These are the numbers being graphed:

resident_mem
 clients              minimum     median    maximum
 50                        50         54         55
100                        96         99        101
150                       129        132        154
200                       160        163        201
250                       205        218        306
300                       275        299        369
350                       369        394        468
400                       436        449        575
450                       542        552        639
500                       555        561        688
550                       707        709        778
600                       710        748        872
650                       696        712        873
700                       868        888        950
747                       800        912        944

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: