<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Performance Tuning on Calgary RHCE</title>
    <link>https://calgaryrhce.ca/categories/performance-tuning/</link>
    <description>Recent content in Performance Tuning on Calgary RHCE</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 20 Oct 2018 17:43:07 +0000</lastBuildDate>
    <atom:link href="https://calgaryrhce.ca/categories/performance-tuning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Troubleshooting performance of VDO and NFS</title>
      <link>https://calgaryrhce.ca/blog/2018/10/20/troubleshooting-performance-of-vdo-and-nfs/</link>
      <pubDate>Sat, 20 Oct 2018 17:43:07 +0000</pubDate>
      <guid>https://calgaryrhce.ca/blog/2018/10/20/troubleshooting-performance-of-vdo-and-nfs/</guid>
      <description>&lt;p&gt;In setting up a local virtualization environment a little while back, I thought I’d try the &lt;a href=&#34;https://www.redhat.com/en/blog/look-vdo-new-linux-compression-layer&#34;&gt;recently GA’d VDO capabilities&lt;/a&gt; in the RHEL 7.5 kernel. These include data compression and de-duplication natively in the linux kernel (through a kernel module). This was Red Hat’s efforts behind the Permabit acquisition. Considering a virtualization data store is a prime candidate for a de-duplication use-case, I was anxious to reclaim some of my storage budget 🙂 . I was also curious to see what the extra overhead was like (if any), and understand the general performance characteristics of VDO.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Migrating RHEV storage domains</title>
      <link>https://calgaryrhce.ca/blog/2018/10/19/migrating-rhev-storage-domains/</link>
      <pubDate>Fri, 19 Oct 2018 21:20:50 +0000</pubDate>
      <guid>https://calgaryrhce.ca/blog/2018/10/19/migrating-rhev-storage-domains/</guid>
      <description>&lt;p&gt;Recently, I’ve been doing some troubleshooting in my virtualization environment, specifically with the NFS storage backing it. To isolate an issue I needed to migrate all the VM disks off the main data store to another one. I hadn’t performed this kind of activity before, but found it to be quite easy. I quickly built an additional NFS server, added it into RHV, and migrated the VM disks to it with just a few clicks and some waiting for the copying to be complete. &lt;a href=&#34;https://access.redhat.com/solutions/736513&#34;&gt;This article&lt;/a&gt; was basic, but helpful.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Getting the most performance out of Openstack, and NFV</title>
      <link>https://calgaryrhce.ca/blog/2017/10/14/getting-the-most-performance-out-of-openstack-and-nfv/</link>
      <pubDate>Sat, 14 Oct 2017 17:33:55 +0000</pubDate>
      <guid>https://calgaryrhce.ca/blog/2017/10/14/getting-the-most-performance-out-of-openstack-and-nfv/</guid>
      <description>&lt;p&gt;By now, most IT staff has either had a chance to deploy OpenStack, or at least are familiar with what it is and what benefits it offers. We’ve moved past the installer race, the fragmentation of “as-a-service” components, and endless TCO calculators. The ecosystem and community has reached a maturity stage where the media and industry alike are calling OpenStack “&lt;a href=&#34;https://major.io/2017/02/24/openstack-isnt-dead-its-boring-thats-a-good-thing/&#34; target=&#34;_blank&#34;&gt;boring&lt;/a&gt;“. &lt;strong&gt;Don’t be fooled, all of these are good things.&lt;/strong&gt; They’re a product of fast-paced innovation seeing a settling of opinions and decision making. OpenStack has reached a maturity point that Linux also hit earlier on in its journey. As linux was (and still is) an incredibly capable and cost-effective option for an OS, OpenStack is also an incredibly capable and cost-effective option for private or public cloud. But now what? What’s next? The answer is deeper and more efficient capability, addressing more edge use-cases, and general polish and integration of all the development that’s happened to date. The low-hanging-fruit development is over, we’re deeper into the less exciting and less headline grabbing work; maximizing the assets as much as we can.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Adding RAM to an old macbook pro</title>
      <link>https://calgaryrhce.ca/blog/2016/09/28/adding-ram-to-an-old-macbook-pro/</link>
      <pubDate>Thu, 29 Sep 2016 01:54:01 +0000</pubDate>
      <guid>https://calgaryrhce.ca/blog/2016/09/28/adding-ram-to-an-old-macbook-pro/</guid>
      <description>&lt;p&gt;I’ve got an old 17″ Macbook Pro from late 2008 that’s still kicking. It’s served me a lot of good years filled with studying, scripting, exams, etc. and I’ve never had a problem with it. I mostly keep it around for testing OSX related things, and as a backup. Last year I replaced the aging 512GB HDD with a 256GB SSD which did wonders to speed it up. This year the battery has finally went on it, so I ebay’d a &lt;a href=&#34;http://www.ebay.ca/itm/112072784618?_trksid=p2057872.m2749.l2649&amp;amp;ssPageName=STRK%3AMEBIDX%3AIT&#34;&gt;replacement&lt;/a&gt; ($25) from &lt;a href=&#34;http://stores.ebay.ca/shopplus86/&#34;&gt;plus_86&lt;/a&gt;. They’re a 3rd party battery replacement shop that ships out of Quebec. I also decided to up the RAM from 2GB to 4GB. Looking back on it, I’m wondering how I ever managed just with 2GB. I had a couple VMs running on this at one time! I ordered a 4GB kit from &lt;a href=&#34;http://stores.ebay.ca/memoryfast/&#34;&gt;memoryfast&lt;/a&gt;, they’ve got a rebate program where I can ship them my old RAM for a small credit to my order, not bad!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Filesystem benchmarking</title>
      <link>https://calgaryrhce.ca/blog/2016/09/11/filesystem-benchmarking/</link>
      <pubDate>Mon, 12 Sep 2016 02:51:38 +0000</pubDate>
      <guid>https://calgaryrhce.ca/blog/2016/09/11/filesystem-benchmarking/</guid>
      <description>&lt;p&gt;Once in a while I need to do some I/O benchmarking. Either when creating a baseline for a before and after performance tuning comparison, or just because I want to see how fast my new SSD/M.2 really is. The tool I find myself going to over the years has been &lt;a href=&#34;http://iozone.org/&#34;&gt;iozone&lt;/a&gt;. I like it because it easily does a myriad of tests that I don’t need to create or think about how to simulate myself, and it’s easily installed on any linux distro. It also outputs the test data into a format that is easily imported into a spreadsheet. I recently added a &lt;a href=&#34;http://www.newegg.ca/Product/Product.aspx?Item=N82E16820147373&#34;&gt;couple SSD&lt;/a&gt;s to my workstation, and finally got around to benchmarking them.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Performance Tweaking – SSDs, I/O Scheduler, Virtual Memory, Browser Cache</title>
      <link>https://calgaryrhce.ca/blog/2014/07/13/performance-tweaking-ssds-io-scheduler-virtual-memory-browser-cache/</link>
      <pubDate>Sun, 13 Jul 2014 22:15:31 +0000</pubDate>
      <guid>https://calgaryrhce.ca/blog/2014/07/13/performance-tweaking-ssds-io-scheduler-virtual-memory-browser-cache/</guid>
      <description>&lt;p&gt;Having recently been exposed to some SSD tweaking at work, I thought I’d do the same with my home PCs.  Prior to this weekend, I’ve just had four 1TB SATA drives in a RAID 5 configuration for a disk setup.  Performance has always been satisfactory, but with recent SSD prices coming down quite a bit, my late 2008 MacBook Pro feeling it’s age, it was time for an upgrade.  Also, it’s been a while since I’ve invested in some new gear for myself, so why not now? ;).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
