<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Compellent on Evan Hoffman</title><link>https://evan.wtf/tags/compellent/</link><description>Recent content in Compellent on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Wed, 21 Dec 2011 23:39:33 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/compellent/index.xml" rel="self" type="application/rss+xml"/><item><title>Compellent "future proof?" Not so much.</title><link>https://evan.wtf/2011/12/21/compellent-future-proof-not-so-much/</link><pubDate>Wed, 21 Dec 2011 23:39:33 +0000</pubDate><guid>https://evan.wtf/2011/12/21/compellent-future-proof-not-so-much/</guid><description>&lt;p&gt;So, I&amp;rsquo;ve written about Compellent a few times from a price perspective, mostly on the disk side. I was recently contacted by our vendor with quotes for two new Compellent controllers. &amp;ldquo;What&amp;rsquo;s this all about?&amp;rdquo; I asked. &amp;ldquo;Why don&amp;rsquo;t we have a call with Compellent to discuss?&amp;rdquo; he replied. I rolled my eyes a little but figured it was worth hearing them out, since our Compellent SAN is at the heart of our infrastructure.&lt;/p&gt;</description></item><item><title>Using WAL archiving &amp; Compellent snapshots for PostgreSQL backups</title><link>https://evan.wtf/2011/07/13/using-wal-archiving-compellent-snapshots-for-postgresql-backups/</link><pubDate>Wed, 13 Jul 2011 13:46:40 +0000</pubDate><guid>https://evan.wtf/2011/07/13/using-wal-archiving-compellent-snapshots-for-postgresql-backups/</guid><description>Changing my Postgres DB backup strategy from nightly &lt;code&gt;pg_dump&lt;/code&gt;s to WAL archiving with SAN snapshots.</description></item><item><title>Migrating a PostgreSQL DB to a new machine without doing a dump &amp; restore</title><link>https://evan.wtf/2011/07/11/migrating-a-postgresql-db-to-a-new-machine-without-doing-a-dump-restore/</link><pubDate>Mon, 11 Jul 2011 14:39:16 +0000</pubDate><guid>https://evan.wtf/2011/07/11/migrating-a-postgresql-db-to-a-new-machine-without-doing-a-dump-restore/</guid><description>rsync over NFS can be so fast.</description></item><item><title>Do I still need swap space?</title><link>https://evan.wtf/2010/11/11/do-i-still-need-swap-space/</link><pubDate>Thu, 11 Nov 2010 14:36:49 +0000</pubDate><guid>https://evan.wtf/2010/11/11/do-i-still-need-swap-space/</guid><description>&lt;p&gt;About three years ago I replaced our primary database. For years we&amp;rsquo;d been plagued by awful performance in the database and we were never able to diagnose the problem. The original server was a real beast at the time: 8 Opterons (single core), 32 gigs ram, and a fibre channel RAID connected via a QLogic HBA. This was back in 2005, so those specs don&amp;rsquo;t probably sound that impressive today, but this was a crazy configuration (with a crazy price tag to match). On paper it looked like this server should be basically invincible but the performance was awful, slowing down every process within the company. We contacted a few different companies (including &lt;a href="http://commandprompt.com/"&gt;CommandPrompt&lt;/a&gt;, which employs several of the core Pg devs) to see if they could assist us in diagnosing the problems but tuning only helped to a point. There was just something wrong with the box, maybe having to do with the FC HBA itself (which nobody knew much about).&lt;/p&gt;</description></item><item><title>Compellent Doesn't Suck</title><link>https://evan.wtf/2010/10/14/compellent-doesnt-suck-2/</link><pubDate>Thu, 14 Oct 2010 11:28:59 +0000</pubDate><guid>https://evan.wtf/2010/10/14/compellent-doesnt-suck-2/</guid><description>&lt;p&gt;I noticed a bunch of people landing on this site by searching for &amp;ldquo;compellent sucks.&amp;rdquo; I just want to avoid any confusion: Compellent doesn&amp;rsquo;t suck. Now that the pain of spending the money to expand our Compellent SAN is in the past, I am back to being in love with the product. The only gripe I&amp;rsquo;ve really ever had with Compellent is the price, and as Ben Franklin said:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;The bitterness of poor quality remains long after the sweetness of low price is forgotten.&lt;/p&gt;</description></item><item><title>Compellent Doesn't Suck</title><link>https://evan.wtf/2010/10/14/compellent-doesnt-suck/</link><pubDate>Thu, 14 Oct 2010 11:28:59 +0000</pubDate><guid>https://evan.wtf/2010/10/14/compellent-doesnt-suck/</guid><description>&lt;p&gt;I noticed a bunch of people landing on this site by searching for &amp;ldquo;compellent sucks.&amp;rdquo; I just want to avoid any confusion: Compellent doesn&amp;rsquo;t suck. Now that the pain of spending the money to expand our Compellent SAN is in the past, I am back to being in love with the product. The only gripe I&amp;rsquo;ve really ever had with Compellent is the price, and as Ben Franklin said:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;The bitterness of poor quality remains long after the sweetness of low price is forgotten.&lt;/p&gt;</description></item><item><title>The VMware datastore LUN 2TB (well, 1.99999 TB) size limit</title><link>https://evan.wtf/2010/09/24/the-vmware-datastore-lun-2tb-well-1-99999-tb-size-limit/</link><pubDate>Fri, 24 Sep 2010 16:00:15 +0000</pubDate><guid>https://evan.wtf/2010/09/24/the-vmware-datastore-lun-2tb-well-1-99999-tb-size-limit/</guid><description>&lt;p&gt;I started migrating our physical machines to VMs using VMware a few years ago and the first problem I ran into is still the most annoying one: the size limit for LUNs is, &lt;a href="http://kb.vmware.com/kb/3371739"&gt;per VMware&amp;rsquo;s docs&lt;/a&gt;, (2TB - 512B). That&amp;rsquo;s 512 bytes shy of 2TB, so basically 1.99999 TB, or 2047.999 GB. So when I create a new LUN for a datastore in the SAN the max size is 2047 GB. Now, as the VMware KB article states, &lt;strong&gt;this is a limitation of SCSI, not VMware per se&lt;/strong&gt;, but that doesn&amp;rsquo;t make it any less annoying. When I first setup ESX, I created a 5 TB LUN for the datastore. It showed up in vCenter as 1 TB. After some Googling I learned of the 2 TB limit &amp;ndash; the usable space is basically usable space = (size of lun) % 2TB, where % is &lt;a href="http://en.wikipedia.org/wiki/Modulo_operation"&gt;the modulo operator&lt;/a&gt; &amp;ndash; and found something suggesting using extents to expand the datastore across luns. I did that, but I later learned that there seems to be a consensus that extents should be avoided.&lt;/p&gt;</description></item><item><title>The bright side of Compellent</title><link>https://evan.wtf/2010/09/22/the-bright-side-of-compellent/</link><pubDate>Wed, 22 Sep 2010 16:07:46 +0000</pubDate><guid>https://evan.wtf/2010/09/22/the-bright-side-of-compellent/</guid><description>&lt;p&gt;Since I was bemoaning Compellent&amp;rsquo;s pricing recently I figured it would be unfair of me not to highlight the upside. Their tagline is (or was when we purchased it) &amp;ldquo;The only SAN so sophisticated it&amp;rsquo;s simple.&amp;rdquo; While I can&amp;rsquo;t say whether they&amp;rsquo;re the ONLY one, the idea is definitely true. This is the first SAN I&amp;rsquo;ve ever used, and aside from the learning curve for iSCSI itself (targets, spinup delay, etc.) it&amp;rsquo;s totally simple and intuitive. Create LUNs, map them to servers. Don&amp;rsquo;t worry about things like RAID levels or hot disks. We&amp;rsquo;re into our second year with Compellent and it&amp;rsquo;s definitely lived up to its promise of simplicity.&lt;/p&gt;</description></item><item><title>Oh, Compellent... again with the disk prices.</title><link>https://evan.wtf/2010/08/25/oh-compellent-again-with-the-disk-prices/</link><pubDate>Wed, 25 Aug 2010 00:57:04 +0000</pubDate><guid>https://evan.wtf/2010/08/25/oh-compellent-again-with-the-disk-prices/</guid><description>&lt;p&gt;Time to expand the SAN again.&lt;/p&gt;&#10;&lt;p&gt;I planned and budgeted for this this year but it still pisses me off. Look, I realize these guys have to make money, but the bottom line is they&amp;rsquo;re charging over $1.40/GB for SATA storage. There are 7200 RPM 2TB SATA drives on &lt;a href="http://amzn.com/B002D5DWZU?tag=evanhoffmasho-20"&gt;Amazon&lt;/a&gt; and &lt;a href="http://www.newegg.com/Product/Product.aspx?Item=N82E16822145298"&gt;Newegg&lt;/a&gt; ranging in price from $130 to $220. That&amp;rsquo;s as low as $0.065/GB. There was even a 2TB WD &amp;ldquo;Green&amp;rdquo; drive (sub-7200 RPM, I think 5900 RPM) &lt;a href="http://slickdeals.net/permadeal/38317"&gt;on Slickdeals&lt;/a&gt; today for $99. That&amp;rsquo;s 5 cents per gig.&lt;/p&gt;</description></item><item><title>The SAN Scam</title><link>https://evan.wtf/2009/04/03/the-san-scam/</link><pubDate>Fri, 03 Apr 2009 11:03:11 +0000</pubDate><guid>https://evan.wtf/2009/04/03/the-san-scam/</guid><description>&lt;p&gt;It&amp;rsquo;s time to buy some more disks for the SAN we have at work. The SAN is made by &lt;a href="http://www.compellent.com/"&gt;Compellent&lt;/a&gt; and we&amp;rsquo;ve had it for a year and it&amp;rsquo;s been great. One of the selling points was the ability to add disks however we wanted - one at a time is possible, which apparently isn&amp;rsquo;t the case with other SAN products. The one we looked at from LeftHand expanded by purchasing entire nodes, so the incremental cost was pretty high. Compellent seemed to have a higher initial cost but cheaper incrementally.&lt;/p&gt;</description></item></channel></rss>