Updated Comparison of C# and Go Performance
Previous Efforts A couple weeks ago I wrote a post that examined performance of the C# and Go programming languages when parsing large XML documents. Why compare C# and Go? Because the goals of the languages are similar: to provide programmers with a statically typed, compiled syntax paired with a runtime that enforces memory safety and automatic garbage collection (reclaiming memory from unreferenced objects). I compared the performance of my C# code with Go code written by Eli Bendersky in his Faster XML Stream Processing in Go blog post. I concluded my C# code ran slightly faster. Then I made […]
The Inherent Conflict Between Bohemian and Militaristic Time Management
My wife and I are training for the Chicago Marathon. My wife has run more than 25 marathons and is fast enough to qualify for Boston- once in 2009 and again last year. She and I have run the Chicago marathon the last three years. I’m quite proud of having completed the marathon three years in a row (26.2 miles is no joke!) but I’m not really in the same league as her. Man, I was suffering for my sins this morning. I had cheated myself of sleep this week and the long distance running Gods noticed (they always do) […]
XML Parsing Performance : C# Versus Go
Interest Piqued Recently I read Eli Bendersky’s Faster XML Stream Processing in Go blog post. While the point of his post was to explain the difference between in-memory and stream parsing, then examine various stream parsing techniques in the Go programming language… I got hung up on his choice of language. Update 2019 Aug 17: I’ve run an apples to apples comparison test. See Updated Comparison of C# and Go Performance Go is a new programming language developed at Google. It’s statically typed, compiled, with a runtime that enforces memory safety and automatic garbage collection (reclaiming memory from unreferenced objects). […]
