<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>iperf on leonroy.</title><link>https://leonroy.com/tags/iperf/</link><description>Recent content in iperf on leonroy.</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Thu, 29 Oct 2015 15:52:35 +0000</lastBuildDate><atom:link href="https://leonroy.com/tags/iperf/index.xml" rel="self" type="application/rss+xml"/><item><title>Benchmarking System Performance</title><link>https://leonroy.com/2015/10/storage-benchmarking/</link><pubDate>Thu, 29 Oct 2015 15:52:35 +0000</pubDate><guid>https://leonroy.com/2015/10/storage-benchmarking/</guid><description>A little knowledge is a dangerous thing. Or so the saying goes. When specifying and buying computer hardware it saves time and money knowing the level of performance you get with your existing equipment and the performance you can expect from your new purchase.
There are numerous metrics to measure but in order to obtain meaningful results (relatively) quickly I personally focus on CPU, memory and file and network I/O.</description></item></channel></rss>