Re: [SR-Users] Kamailio benchmark app_python + OPTIONS

2016-06-13 Thread Daniel-Constantin Mierla
On 12/06/16 10:56, Anonim Stefan wrote: > Hi, > > I am doing some basic benchmarks with Kamailio. I am using a VM with 1 > CPU i7 2,50 GHz and Kamailio with children=1. > > This is what I measure for each request, inside the benchmark block: > - app_python processing (some euclidian distance base

Re: [SR-Users] Kamailio benchmark app_python + OPTIONS

2016-06-12 Thread Anonim Stefan
And the basic SIPp test file. Stefan On Sun, Jun 12, 2016 at 10:44 PM, Anonim Stefan wrote: > Hi Konstantin, > > This is the config+script I tested with (note: commented while). I tested > with OPTIONS SIPp requests. > > Thanks, > Stefan > > > On Sun, Jun 12, 2016 at 12:08 PM, Konstantin M. >

Re: [SR-Users] Kamailio benchmark app_python + OPTIONS

2016-06-12 Thread Anonim Stefan
Hi Konstantin, This is the config+script I tested with (note: commented while). I tested with OPTIONS SIPp requests. Thanks, Stefan On Sun, Jun 12, 2016 at 12:08 PM, Konstantin M. wrote: > Hi, > > Could you please include config and python script? > > 2016-06-12 12:03 GMT+03:00 Anonim Stefan

Re: [SR-Users] Kamailio benchmark app_python + OPTIONS

2016-06-12 Thread Konstantin M.
Hi, Could you please include config and python script? 2016-06-12 12:03 GMT+03:00 Anonim Stefan : > One more detail would be that I set the granularity equal to the call > rate, but still I'm looking at the global average. > > ___ > SIP Express Router

Re: [SR-Users] Kamailio benchmark app_python + OPTIONS

2016-06-12 Thread Anonim Stefan
One more detail would be that I set the granularity equal to the call rate, but still I'm looking at the global average. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/

[SR-Users] Kamailio benchmark app_python + OPTIONS

2016-06-12 Thread Anonim Stefan
Hi, I am doing some basic benchmarks with Kamailio. I am using a VM with 1 CPU i7 2,50 GHz and Kamailio with children=1. This is what I measure for each request, inside the benchmark block: - app_python processing (some euclidian distance based on a dlg_var input) -> same for all requests - uac_r