coding:oops
Apr. 7th, 2005 08:08 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
tn3270Have a large chunk of fairly CPU intensive code working and am working improve its performance. I did a project that was a performance improvement. However, I made a teeny mistake, and caused a lot of code to not be called when it should have. This made my performance improvement seem about twice as good as it really was. The program runs much quicker if it skips a lot of processing, sadly the result was not correct.
A few years ago, I remember this type of thing happening to someone I worked with. He made modest change and all of a sudden the program ran 10 times as fast, everyone was very pleased since we regularly got beat up for the slowness of the program. Turns out, he accidentally commented out the call to the function that did all of the work.
I got a little taste of this today. Oh well.
A few years ago, I remember this type of thing happening to someone I worked with. He made modest change and all of a sudden the program ran 10 times as fast, everyone was very pleased since we regularly got beat up for the slowness of the program. Turns out, he accidentally commented out the call to the function that did all of the work.
I got a little taste of this today. Oh well.
