Ejabberd resource tests/try 7

From OLPC

< Ejabberd resource tests
Revision as of 02:23, 21 November 2008 by Douglas (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Try 7: Shared roster with old TLS code

A repeat of Ejabberd resource tests/try 6, using the old TLS code.

This one crashed at 700 users.

Memory use

Image:try7-users_active_vs_resident_mem.png

Image:try7-psmem-resident_mem-virtual_mem.png

Memory use vs connections

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

Image:try7-resident_mem_min_per_conn-resident_mem_max_per_conn-resident_mem_median_per_conn.png

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:

Image:try7-virtual_mem_min_per_conn-virtual_mem_max_per_conn-virtual_mem_median_per_conn.png


CPU usage

Cumulative CPU use by the ejabberd process:

Image:try7-users_active_vs_cputime.png

Load averages, by connections and by time:

Image:try7-load_avg_5_min_per_conn-load_avg_5_max_per_conn-load_avg_5_median_per_conn.png

Image:try7-load_avg_1-load_avg_5-load_avg_15.png

Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox
In other languages