Wednesday, June 29, 2005


So today at work, about 3:30, my boss walks up with two sheets of paper, and says we've got a problem. He proceeds to show me a printing operation that takes about 45 seconds. So there I was, spending the next two hours frantically trying to figure out what the problem was, especially since we're trying to get a solid release out soon.

So the point is, when debuggin for a performance issue, the assumption of what is causing the problem is probably correct. I noticed that the server (it's a client/server architecture) was being hit very hard, and rather than just go down that path right away and check what I thought the problem was, I did it the hard way. Granted it only took two hours to find and fix, it still sucked that I didn't try to do the obvious.

But oh well, you live and learn.


Post a Comment

<< Home