Ejabberd resource tests/try 8

From OLPC
Jump to: navigation, search

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

Try8-users active vs resident mem.png

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).

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

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:

Try8-users active vs cputime.png

Load averages, by connections and by time:

Try8-load avg 5 min per conn-load avg 5 max per conn-load avg 5 median per conn.png

Try8-load avg 1-load avg 5-load avg 15.png

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Ejabberd_resource_tests/try_8&oldid=182943"