Benchmark Module

Bastian Friedrich

   Collax GmbH

Daniel-Constantin Mierla

   Voice System SRL

Edited by

Bastian Friedrich

   Copyright © 2007 Collax GmbH

   Copyright © 2007 Voice System SRL
     __________________________________________________________

   Table of Contents
   1. User's Guide

        1.1. Overview
        1.2. Dependencies

              1.2.1. OpenSER Modules
              1.2.2. External Libraries or Applications

        1.3. Exported Parameters

              1.3.1. enable (int)
              1.3.2. granularity (int)
              1.3.3. loglevel (int)

        1.4. Exported Functions

              1.4.1. bm_start_timer(name)
              1.4.2. bm_log_timer(name)

        1.5. Exported MI Functions

              1.5.1. bm_enable_global
              1.5.2. bm_enable_timer
              1.5.3. bm_granularity
              1.5.4. bm_loglevel

        1.6. Example of usage

   2. Developer's Guide

        2.1. Available Functions

              2.1.1. bm_register(name, mode, id)
              2.1.2. bm_start(id)
              2.1.3. bm_log(id)
              2.1.4. Benchmark API Example

   3. Frequently Asked Questions

   List of Examples
   1-1. Set enable parameter
   1-2. Set granularity parameter
   1-3. Set loglevel parameter
   1-4. bm_start_timer usage
   1-5. bm_log_timer usage
   1-6. Enabling a timer
   1-7. benchmark usage
   2-1. Using the benchmark module's API from another module
     __________________________________________________________

Chapter 1. User's Guide

1.1. Overview

   This module helps developers to benchmark their module
   functions. By adding this module's functions via the
   configuration file or through its API, OpenSER can log
   profiling information for every function.

   The duration between calls to start_timer and log_timer is
   stored and logged via OpenSER's logging facility. Please note
   that all durations are given as microseconds (don't confuse
   with milliseconds!).
     __________________________________________________________

1.2. Dependencies

1.2.1. OpenSER Modules

   The following modules must be loaded before this module:

     * No dependencies on other OpenSER modules.
     __________________________________________________________

1.2.2. External Libraries or Applications

   The following libraries or applications must be installed
   before running OpenSER with this module loaded:

     * None.
     __________________________________________________________

1.3. Exported Parameters

1.3.1. enable (int)

   Even when the module is loaded, benchmarking is not enabled per
   default. This variable may have three different values:

     * -1 - Globally disable benchmarking
     * 0 - Enable per-timer enabling. Single timers are inactive
       by default and can be activated through the MI interface as
       soon as that feature is implemented.
     * 1 - Globally enable benchmarking

   Default value is "0".

   Example 1-1. Set enable parameter
...
modparam("benchmark", "enable", 1)
...
     __________________________________________________________

1.3.2. granularity (int)

   Logging normally is not done for every reference to the
   log_timer() function, but only every n'th call. n is defined
   through this variable. A sensible granularity seems to be 100.

   Default value is "1".

   Example 1-2. Set granularity parameter
...
modparam("benchmark", "granularity", 500)
...
     __________________________________________________________

1.3.3. loglevel (int)

   Set the log level for the benchmark logs. These levels should
   be used:

     * -3 - L_ALERT
     * -2 - L_CRIT
     * -1 - L_ERR
     * 1 - L_WARN
     * 2 - L_NOTICE
     * 3 - L_INFO
     * 4 - L_DBG

   Default value is "3" (L_INFO).

   Example 1-3. Set loglevel parameter
...
modparam("benchmark", "loglevel", 4)
...

   This will set the logging level to L_DBG.
     __________________________________________________________

1.4. Exported Functions

1.4.1. bm_start_timer(name)

   Start timer "name". A later call to "bm_log_timer()" logs this
   timer..

   Example 1-4. bm_start_timer usage
...
bm_start_timer("test");
...
     __________________________________________________________

1.4.2. bm_log_timer(name)

   This function logs the timer with the given ID. The following
   data are logged:

     * Last msgs is the number of calls in the last logging
       interval. This equals the granularity variable.

     * Last sum is the accumulated duration in the current logging
       interval (i.e. for the last "granularity" calls).

     * Last min is the minimum duration between start/log_timer
       calls during the last interval.

     * Last max - maximum duration.

     * Last average is the average duration between
       bm_start_timer() and bm_log_timer() since the last logging.

     * Global msgs number of calls to log_timer.

     * Global sum total duration in microseconds.

     * Global min... You get the point. :)

     * Global max also obvious.

     * Global avg possibly the most interesting value.

   Example 1-5. bm_log_timer usage
...
bm_log_timer("test");
...
     __________________________________________________________

1.5. Exported MI Functions

1.5.1. bm_enable_global

   Enables/disables the module. Parameter may be -1, 0 or 1. See
   discription of "enable" parameter.
     __________________________________________________________

1.5.2. bm_enable_timer

   Enable or disable a single timer. The following example enables
   timer "test" (the second parameter must be 0 to disable):

   Example 1-6. Enabling a timer
...
openserctl fifo bm_enable_timer test 1
...
     __________________________________________________________

1.5.3. bm_granularity

   Modifies the benchmarking granularity. See "granularity"
   variable.
     __________________________________________________________

1.5.4. bm_loglevel

   Modifies the module log level. See "loglevel" variable.
     __________________________________________________________

1.6. Example of usage

   Measure the duration of user location lookup.

   Example 1-7. benchmark usage
...
bm_start_timer("usrloc-lookup");
lookup("location");
bm_log_timer("usrloc-lookup");
...
     __________________________________________________________

Chapter 2. Developer's Guide

   The benchmark module provides an internal API to be used by
   other OpenSER modules. The available functions are identical to
   the user exported functions.

   Please note that this module is intended mainly for developers.
   It should be used with caution in production environments.
     __________________________________________________________

2.1. Available Functions

2.1.1. bm_register(name, mode, id)

   This function register a new timer and/or returns the internal
   ID associated with the timer. mode controls the creation of new
   timer if not found. id is to be used by start and log timer
   functions.
     __________________________________________________________

2.1.2. bm_start(id)

   This function equals the user-exported function bm_start_timer.
   The id is passed as an integer, though.
     __________________________________________________________

2.1.3. bm_log(id)

   This function equals the user-exported function bm_log_timer.
   The id is passed as an integer, though.
     __________________________________________________________

2.1.4. Benchmark API Example

   Example 2-1. Using the benchmark module's API from another
   module
...
#include "../benchmark/benchmark.h"
...
struct bm_binds bmb;
...
...
/* load the benchmarking API */
if (load_bm_api( &bmb )!=0) {
    LM_ERR("can't load benchmark API\n");
    goto error;
}
...
...
/* Start/log timers during a (usually user-exported) module function */
bmp.bm_register("test", 1, &id)
bmb.bm_start(id);
do_something();
bmb.bm_log(id);
...
     __________________________________________________________

Chapter 3. Frequently Asked Questions

   3.1. Where can I find more about OpenSER?
   3.2. Where can I post a question about this module?
   3.3. How can I report a bug?

   3.1. Where can I find more about OpenSER?

   Take a look at http://www.openser.org/.

   3.2. Where can I post a question about this module?

   First at all check if your question was already answered on one
   of our mailing lists:

     * User Mailing List -
       http://lists.openser.org/cgi-bin/mailman/listinfo/users
     * Developer Mailing List -
       http://lists.openser.org/cgi-bin/mailman/listinfo/devel

   E-mails regarding any stable OpenSER release should be sent to
   <users@lists.openser.org> and e-mails regarding development
   versions should be sent to <devel@lists.openser.org>.

   If you want to keep the mail private, send it to
   <team@lists.openser.org>.

   3.3. How can I report a bug?

   Please follow the guidelines provided at:
   http://sourceforge.net/tracker/?group_id=139143.
