[Users] call performance

Klaus Darilion klaus.mailinglists at pernau.at
Mon Jul 24 13:39:49 CEST 2006


Hi!

I tried to test openser's call setup performance.
Scenario: INVITE - 180 - 200

Server: 2 x P3 1266MHz

listen=UDP:...
children=100

I used SIPP for testing.

1. Although the config is rather simple (no DNS, no DB, no lookup) I 
can't get more than 700 INVITE transactions per second. Shouldn't this 
be higher (AFAIK ser powers the whole bay area on a handheld PC)?

2. With children = 100, I can see more than 200 threads and lots of unix 
sockets opened, although no DB is used. Why?

3. openser core dumps when children=200


regards
klaus


#
# $Id: openser.cfg,v 1.5 2005/10/28 19:45:33 bogdan_iancu Exp $
#
# simple quick-start config script
#

# ----------- global configuration parameters ------------------------

debug=3            # debug level (cmd line: -dddddddddd)
fork=yes
log_stderror=no    # (cmd line: -E)

/* Uncomment these lines to enter debugging mode
fork=no
log_stderror=yes
*/

check_via=no    # (cmd. line: -v)
dns=no          # (cmd. line: -r)
rev_dns=no      # (cmd. line: -R)
port=5060
children=100
fifo="/tmp/openser_fifo"

listen=udp:83.136.32.132:5060
#listen=tcp:83.136.32.132:5060
#listen=tls:83.136.32.132:5061

#
# uncomment the following lines for TLS support
#disable_tls = 0
#tls_verify_client = 0
#tls_verify_server = 0
#tls_require_client_certificate = 0
#tls_method = TLSv1
#tls_certificate = "/etc/openser/tls/user/user-cert.pem"
#tls_private_key = "/etc/openser/tls/user/user-privkey.pem"
#tls_ca_list = "/etc/openser/tls/user/user-calist.pem"

# ------------------ module loading ----------------------------------

# Uncomment this if you want to use SQL database
#loadmodule "/usr/lib/openser/modules/mysql.so"

loadmodule "/usr/lib/openser/modules/sl.so"
loadmodule "/usr/lib/openser/modules/tm.so"
loadmodule "/usr/lib/openser/modules/rr.so"
loadmodule "/usr/lib/openser/modules/maxfwd.so"
loadmodule "/usr/lib/openser/modules/usrloc.so"
loadmodule "/usr/lib/openser/modules/registrar.so"
loadmodule "/usr/lib/openser/modules/textops.so"
loadmodule "/usr/lib/openser/modules/avpops.so"
loadmodule "/usr/lib/openser/modules/xlog.so"

# Uncomment this if you want digest authentication
# mysql.so must be loaded !
#loadmodule "/usr/lib/openser/modules/auth.so"
#loadmodule "/usr/lib/openser/modules/auth_db.so"

# ----------------- setting module-specific parameters ---------------

# -- usrloc params --

modparam("usrloc", "db_mode",   0)

# Uncomment this if you want to use SQL database
# for persistent storage and comment the previous line
#modparam("usrloc", "db_mode", 2)

# -- auth params --
# Uncomment if you are using auth module
#
#modparam("auth_db", "calculate_ha1", yes)
#
# If you set "calculate_ha1" parameter to yes (which true in this config),
# uncomment also the following parameter)
#
#modparam("auth_db", "password_column", "password")

# -- rr params --
# add value to ;lr param to make some broken UAs happy
modparam("rr", "enable_full_lr", 1)

# -------------------------  request routing logic -------------------

# main routing logic

route{

         # initial sanity checks -- messages with
         # max_forwards==0, or excessively long requests
         if (!mf_process_maxfwd_header("10")) {
                 sl_send_reply("483","Too Many Hops");
                 exit;
         };

         if (msg:len >=  2048 ) {
                 sl_send_reply("513", "Message too big");
                 exit;
         };

         # we record-route all messages -- to make sure that
         # subsequent messages will go through our proxy; that's
         # particularly good if upstream and downstream entities
         # use different transport protocol
         if (!method=="REGISTER")

                 record_route();

         # subsequent messages withing a dialog should take the
         # path determined by record-routing
         if (loose_route()) {
                 # mark routing logic in request
                 append_hf("P-hint: rr-enforced\r\n");
                 route(1);
         };

avp_printf("$avp(s:target)","sip:83.136.32.134;transport=udp");
avp_pushto("$ru","$avp(s:target)");

t_relay();
exit;

         if (!uri==myself) {
                 # mark routing logic in request
                 append_hf("P-hint: outbound\r\n");
                 # if you have some interdomain connections via TLS
                 #if(uri=~"@tls_domain1.net") {
                 #       t_relay_to_tls("IP_domain1","port_domain1");
                 #       exit;
                 #} else if(uri=~"@tls_domain2.net") {
                 #       t_relay_to_tls("IP_domain2","port_domain2");
                 #       exit;
                 #}
                 route(1);
         };

         # if the request is for other domain use UsrLoc
         # (in case, it does not work, use the following command
         # with proper names and addresses in it)
         if (uri==myself) {

                 if (method=="REGISTER") {

                         # Uncomment this if you want to use digest 
authentication
                         #if (!www_authorize("openser.org", "subscriber")) {
                         #       www_challenge("openser.org", "0");
                         #       exit;
                         #};

                         save("location");
                         exit;
                 };

                 lookup("aliases");
                 if (!uri==myself) {
                         append_hf("P-hint: outbound alias\r\n");
                         route(1);
                 };
                 # native SIP destinations are handled using our USRLOC DB
                 if (!lookup("location")) {
                         sl_send_reply("404", "Not Found");
                         exit;
                 };
                 append_hf("P-hint: usrloc applied\r\n");
         };

         route(1);
}


route[1] {
         # send it out now; use stateful forwarding as it works reliably
         # even for UDP2TCP
         if (!t_relay()) {
                 sl_reply_error();
         };
         exit;
}





More information about the Users mailing list