I need this done in the next 15 seconds!
j/k, of course.
I wrote a program in a different language (ObjectPAL) a couple years ago, and execution speed was very (X100) important to my boss, so much so that he made us replace every if statement with a switch statement with only one case, because he said it was faster. So - would that be language specific, or is it a difference that could be attributed to the difference in data structures? Which one's faster in C?
-Govtcheez
[email protected]
I can't see how that would be faster. A good compiler should generate the same machine code for both the if and switch/case strategy.
>because he said it was faster
I don't know of any speed difference between and if and a switch with one case. The if will take a value and test it against another value and if the result is true then the body is executed. The switch takes a value and tests it against a series of values, but in this case it only tests against one and if it is true the body is executed. Provided that no break statement is included in the one case switch they should perform equally.
I would imagine that a switch with multiple cases would perform more efficiently than an if..else construct with the same tests because the switch only acquires the original value once, just like foo += 1, foo is only accessed once instead of twice in the longer version foo = foo + 1;.
>execution speed was very (X100) important
Fiddling around with the comparisons and smaller stuff should be done after the most efficient algorithm has been designed. You won't see as much of a speed increase by changing ifs to switches than you would if the program as a whole were redesigned to be efficient. Though you may have already done this at the time, most bosses concerned with efficiency and speed won't look at the big picture.
>would that be language specific
Probably
-Prelude
My best code is written with the delete key.
> so much so that he made us replace every if statement with a switch statement
And was it quicker?
And was it just technically quicker (like you need an oscilloscope), or was is really quicker from a user perspective?
Did anyone actually bother to measure the before and after case?
Think about what you actually did - the hugely significant part of an if statement is the expression, not the jump if true/false, which even the lamest of compilers would have trouble generating more than a handful of instructions for.
In C, they would have to be of the form
if ( var == CONSTANT )
for that hack to work, and it's only at this level of simplicity that the time spent evaluating the condition, and the subsequent jumps become comparable.
As Prelude said, its pointless micro-optimising until you've chosen the best algorithm.
It's also pointless taking a blanket approach, without having profiled the code to find out where it really is spending the most time. Saving 1uS in some initialisation code which is run just once is not value for money.
> would that be language specific
- The language, the compiler, the version of the compiler, the compilation options.
> And was it quicker?
Not noticeably, no... However, I wasn't exactly in a position to argue with him.
Don't blame me for this - it was his idea, and I never said it was a good one.
-Govtcheez
[email protected]
