<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance on mcclain.sh</title><link>http://mcclain.sh/tags/performance/</link><description>Recent content in Performance on mcclain.sh</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 15 Sep 2022 00:00:00 +0000</lastBuildDate><atom:link href="http://mcclain.sh/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Benchmarking in Go</title><link>http://mcclain.sh/posts/go-benchmarking/</link><pubDate>Thu, 15 Sep 2022 00:00:00 +0000</pubDate><guid>http://mcclain.sh/posts/go-benchmarking/</guid><description>&lt;p&gt;As a hobbyist Gopher, I still discover things about the language that surprise me. While working on a side project, I found myself trying to decide between two implementations where speed was a major factor. As it would turn out, Go actually has some great benchmarking tools! What better way to answer my question than to put them head-to-head?&lt;/p&gt;
&lt;p&gt;In this blog, We&amp;rsquo;ll work through a couple examples to learn exactly how to write these benchmarks, as well as how we dive deeper into the results. Overall speed is great, but what’s even better is getting to put things under a microscope and fine-tune them. Let’s start with how to write a benchmark with a simple example.&lt;/p&gt;</description></item></channel></rss>