16 Oct
2007
16 Oct
'07
3:03 p.m.
Hi, I'm wondering which solution (A or B) is more efficient in case method is
NOT an INVITE:
A) if ( (method=="INVITE") && (isflagset(5) || isbflagset(6)) )
B) if ( mehtod=="INVITE" )
My question is: Is faster B because does less comparasions?
or does OpenSer break A conditional during first condition (method=="INVITE")
because it's false so then A and B are equally efficient?
And which is more efficient (C or D) when all the conditions are true?
C) if ( (method=="INVITE") && (isflagset(5) || isbflagset(6)) ) {
....
D) if ( method=="INVITE" ) {
if ( (isflagset(5) || isbflagset(6)) ) {
...
Thanks for any explanation.
Best regards.
--
Iñaki Baz Castillo
ibc(a)in.ilimit.es
16 Oct
16 Oct
3:18 p.m.
Iñaki Baz Castillo wrote:
Hi, I'm wondering which solution (A or B) is more
efficient in case method is
NOT an INVITE:
A) if ( (method=="INVITE") && (isflagset(5) || isbflagset(6)) )
B) if ( mehtod=="INVITE" )
AFAIK the conditions are checked in the order they appear and stop as
soon as possible. In your case in != INVITE it should be the same.
Further, if you use is_method("INVITE") it is even faster.
regards
klaus
My question is: Is faster B because does less comparasions?
or does OpenSer break A conditional during first condition (method=="INVITE")
because it's false so then A and B are equally efficient?
And which is more efficient (C or D) when all the conditions are true?
C) if ( (method=="INVITE") && (isflagset(5) || isbflagset(6)) ) {
....
D) if ( method=="INVITE" ) {
if ( (isflagset(5) || isbflagset(6)) ) {
...
Thanks for any explanation.
Best regards.
3:33 p.m.
El Tuesday 16 October 2007 15:18:58 Klaus Darilion escribió:
Iñaki Baz Castillo wrote:
Nice to know it.
Hi, I'm wondering which solution (A or B) is
more efficient in case
method is NOT an INVITE:
A) if ( (method=="INVITE") && (isflagset(5) || isbflagset(6)) )
B) if ( mehtod=="INVITE" )
AFAIK the conditions are checked in the order they appear and stop as
soon as possible. In your case in != INVITE it should be the same. Further, if you use is_method("INVITE") it
is even faster.
Ops, I didn't know that. Ok, I'll change all my script :)
Thanks again.
--
Iñaki Baz Castillo
ibc(a)in.ilimit.es
3:34 p.m.
Hi,
AFAIK the conditions are checked in the order they
appear and stop as
soon as possible. In your case in != INVITE it should be the same.
Further, if you use is_method("INVITE") it is even faster.
To be honest, I don't think it really cares in standard scenarios. An
optimization of some microseconds is next to nothing compared to the
duration it takes to perform a db or radius request for example.
Just my 2 cents,
Andreas
4:34 p.m.
Andreas Granig wrote:
Hi,
that's true
AFAIK the conditions are checked in the order
they appear and stop as
soon as possible. In your case in != INVITE it should be the same.
Further, if you use is_method("INVITE") it is even faster.
To be honest, I don't think it really cares in standard scenarios. An
optimization of some microseconds is next to nothing compared to the
duration it takes to perform a db or radius request for example. 
5:05 p.m.
Hello,
if one is concerned about the efficiency of some config snippets, then
use the benchmark module to see which is faster. Practically, that is
the scope of the module.
Cheers,
Daniel
PS. Indeed, the conditionals try to stop as soon as possible in case of
and/or tests.
On 10/16/07 17:34, Klaus Darilion wrote:
Andreas Granig wrote:
Hi,
that's true
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
AFAIK the conditions are checked in the order
they appear and stop
as soon as possible. In your case in != INVITE it should be the same.
Further, if you use is_method("INVITE") it is even faster.
To be honest, I don't think it really cares in standard scenarios. An
optimization of some microseconds is next to nothing compared to the
duration it takes to perform a db or radius request for example.
5:05 p.m.
El Tuesday 16 October 2007 15:34:15 Andreas Granig escribió:
Hi,
About duration sure you are right, but what about CPU usage?
An external DB or Radius query can take long time but during that time the CPU
is no used as if it's doing routing.
--
Iñaki Baz Castillo
ibc(a)in.ilimit.es
AFAIK the conditions are checked in the order
they appear and stop as
soon as possible. In your case in != INVITE it should be the same.
Further, if you use is_method("INVITE") it is even faster.
To be honest, I don't think it really cares in standard scenarios. An
optimization of some microseconds is next to nothing compared to the
duration it takes to perform a db or radius request for example.
6256
days inactive
6256
days old
6 comments
4 participants
participants (4)
-
Andreas Granig -
Daniel-Constantin Mierla -
Iñaki Baz Castillo -
Klaus Darilion