If the Procedure is taking seconds to run then for sure any parse will be trivial, by comparison, but parse is mostly pure CPU. Every system I have ever worked on has had improve compile/parse times from compressed source code because the parser doesn't have to step-over the whitespace and comments; unless computer science has moved on there is no easy way to "know" where the next keyword is in the file, it is found by walking the characters in the line sequentially, ignoring any spaces etc.. I agree that it is not a reason to work with poorly formatted code, but if it turns out to make even a modest saving it would be a reason to consider compressing the source code prior to deployment. For some, such as me, some obfuscation is welcome too.
That said, right now I'd just like to make a performance test, and I'd appreciate any ideas folk have as to the best way of doing that.