Stefan Mititelu has shared some statistics about stressing Kamailio on a Raspberry PI 3 device. All the relevant details were made available at:

Here are device’s characteristics

An over-clocked Raspberry PI 3 running Raspbian Stretch with a U3 MicroSD card.

pi@raspberrypi:~ $ cat /etc/issue
 Raspbian GNU/Linux 9 \n \l
 pi@raspberrypi:~ $ uname -a
 Linux raspberrypi 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/Linux

 pi@raspberrypi:~ $ cat /boot/config.txt

His remarks on Kamailio’s sr-users mailing list:

The tests ran for 60 seconds, repeated a couple of times, and they were done in a LAN, using PI’s ethernet interface, running Kamailio 5.1.1.

  1. REGISTER/200, __with db_text__
    – at 900 cps test did finish: all UAC registered; pi htop threads were ~15-20%
    – at 950 cps test did NOT finish: got “Overload warning” on my UAC/UAS SIPp testing machine
  2. INVITE/180/200/PAUSE(3sec)/BYE/200, __with no media__
    – at 370 cps test did finish: all UAC->UAS calls completed; ~150 “180 Trying” Unexpected-Msg on UAC side; pi htop threads were ~50%
    – at 380 cps test did NOT finish: few(~5) UAC->UAS calls not completed; pi htop threads were ~50%

The results are really impressive (even if the used testing configs were really basic ones)!!!

Moreover, I think that I’ve reached the limit of my current SIPp testing machine, but not of PI’s.

Should you have something interesting to share about using Kamailio, do not hesitate to contact us, we will gladly publish an article on our website.

Thanks for flying Kamailio!