Forum Discussion
simple if statements optimized to switch statements ?
Is there a performance advantage to optimizing the simplest type of if statements as switch statements ?
EXAMPLE 1 :
if { [string tolower [HTTP::path]] eq "somepage.html" } {
pool pool-01
}
...
Kevin_Stewart
Employee
EmployeeI'm surprised it's more optimal to evaluate an expression each time rather storing the result in a variable
The thing is, you're not performing an evaluation with these protocol commands (ie. [HTTP::path]). The information is already stored in the state table for this request, so [HTTP::path] is itself a variable, more or less.
in EXAMPLE 2 , because two comparisons are performed you'd prefer a switch over an if ?
You can really go either way with 1 to 10 comparisons, but I think anything more than that just turns into confusing code. It's a matter of preference more than performance.
