Ejabberd resource tests/try 8

From OLPC

Jump to: navigation, search

Contents

Try 8: Shared roster with new TLS code and Postgres database

Up until Ejabberd resource tests/try 7, Mnesia was used.

postgres used up to 12MB of ram for itself.

Memory use

Image:try8-users_active_vs_resident_mem.png

Image:try8-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:try8-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            115      119      127
    100            148      154      160
    150            189      192      220
    200            238      242      281
    250            269      274      339
    300            358      369      393
    350            416      428      509
    400            515      530      605
    450            597      607      737
    500            645      648      818
    550            801      806      882
    600            764      788      912
    650            693      799      937
    700            790      837      934


Virtual memory

Image:try8-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:try8-users_active_vs_cputime.png

Load averages, by connections and by time:

Image:try8-load_avg_5_min_per_conn-load_avg_5_max_per_conn-load_avg_5_median_per_conn.png

Image:try8-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