News for hackers. Stuff that matters.
Re:IronPython vs cPython benchmarks by jules on Thursday March 18, 2010 @09:34AM (#1201222)
Interesting that IronPython is faster than CPython at processing exception handlers when no exception is thrown, but much slower at throwing.
Re:IronPython vs cPython benchmarks by torial on Thursday March 18, 2010 @06:36PM (#1202726)
I remember when FePy was first coming out, and Jim Hugunin was encountering considerable slowness in regard to exceptions, and he conferred with Guido about it because the fail-first idiom is a preferred python strategy. Anyways, Guido was like, you are functionally equivalent so it doesn't matter. (I'm just regurgitating my rough memory of Jim's blog about it.) But that was also the first time I learned how disruptive an exception was to .Net program flow. I've also seen it in general with other .Net languages -- exceptions kill performance, and defensive programming is very worth the extra effort.
Re:IronPython vs cPython benchmarks by 0x7feb38ad on Thursday March 18, 2010 @11:44AM (#1201566)
Just goes to show how important it is to bug-free code when developing on the .NET platform. You don't want those exceptions slow down you're code.