Ejabberd resource tests/try 5: Difference between revisions

From OLPC
Jump to navigation Jump to search
(New page: === Try 5: a few hundred users, interacting properly === It turns out that , hyperactivity was not Image:users_active_vs_cputime.png [[Image:resident_mem_min_per_conn-resident_mem...)
 
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
=== Try 5: a few hundred users, interacting properly ===
== Try 5: a few hundred users, interacting properly ==


It turns out that , hyperactivity was not
It turns out that in the hyperactivity agents were not interacting in
[[Ejabberd resource tests/try 4]], due to the shared roster being off by mistake.


For this test several hyperactivity instances were used, each running 50 clients. 4 XO laptops were also connected, so the total number of clients was at most stages 50n + 4.
⚫
[[Image:users_active_vs_cputime.png]]


=== 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.
⚫
[[Image:resident_mem_min_per_conn-resident_mem_max_per_conn-resident_mem_median_per_conn.png]]


[[Image:psmem-resident_mem-virtual_mem.png]]
[[Image:try5-users_active_vs_resident_mem.png]]


[[Image:try5-psmem-resident_mem-virtual_mem.png]]


=== Memory use vs connections ===
⚫
[[Image:load_avg_5_min_per_conn-load_avg_5_max_per_conn-load_avg_5_median_per_conn.png]]


This shows max-median-min values for stable points along the way (3 minutes with the same number of connections).


⚫
[[Image:try5-resident_mem_min_per_conn-resident_mem_max_per_conn-resident_mem_median_per_conn.png]]
[[Image:users_active_vs_resident_mem.png]]


Here's the raw data (duplicates exist because a number of connections can vary slightly as clients disconnect and reconnect).
⚫
[[Image:hyperactivity-3-800.jpg]]

resident_mem
clients minimum median maximum
54 96 97 98
104 134 139 143
154 164 167 174
204 220 224 253
204 229 232 236
254 270 278 289
304 345 399 421
254 329 348 386
304 337 352 419
354 455 471 515
403 499 577 654
404 502 504 514
454 635 644 696
453 642 644 646
454 608 613 664

=== CPU usage ===

Cumulative CPU use by the ejabberd process:

⚫
[[Image:try5-users_active_vs_cputime.png]]

Load averages, by connections and by time:

⚫
[[Image:try5-load_avg_5_min_per_conn-load_avg_5_max_per_conn-load_avg_5_median_per_conn.png]]

[[Image:try5-load_avg_1-load_avg_5-load_avg_15.png]]


=== The laptops ===

Note that they all see a different number of clients.

⚫
[[Image:try5-hyperactivity-3-800.jpg]]

Latest revision as of 03:22, 4 November 2008

Try 5: a few hundred users, interacting properly

It turns out that in the hyperactivity agents were not interacting in Ejabberd resource tests/try 4, due to the shared roster being off by mistake.

For this test several hyperactivity instances were used, each running 50 clients. 4 XO laptops were also connected, so the total number of clients was at most stages 50n + 4.

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.

Try5-users active vs resident mem.png

Try5-psmem-resident mem-virtual mem.png

Memory use vs connections

This shows max-median-min values for stable points along the way (3 minutes with the same number of connections).

Try5-resident mem min per conn-resident mem max per conn-resident mem median per conn.png

Here's the raw data (duplicates exist because a number of connections can vary slightly as clients disconnect and reconnect). 

resident_mem
clients              minimum     median    maximum
54                        96         97         98
104                      134        139        143
154                      164        167        174
204                      220        224        253
204                      229        232        236
254                      270        278        289
304                      345        399        421
254                      329        348        386
304                      337        352        419
354                      455        471        515
403                      499        577        654
404                      502        504        514
454                      635        644        696
453                      642        644        646
454                      608        613        664

CPU usage

Cumulative CPU use by the ejabberd process:

Try5-users active vs cputime.png

Load averages, by connections and by time:

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

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


The laptops

Note that they all see a different number of clients.

Try5-hyperactivity-3-800.jpg

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