<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:admin="http://webns.net/mvcb/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
    
    <title>c0t0d0s0.org - Comments</title>
    <link>http://www.c0t0d0s0.org/</link>
    <description>c0t0d0s0.org - the sun in a lighthungry universe</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.6 - http://www.s9y.org/</generator>
    
    

<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/C0t0d0s0orgKommentare" /><feedburner:info uri="c0t0d0s0orgkommentare" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:browserFriendly>This is an XML content feed. It is intended to be viewed in a newsreader or syndicated to another site, subject to copyright and fair use.</feedburner:browserFriendly><item>
    <title>Woo: IOPS, capacity, bandwidth - and something new to explain to the people in purchasing</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/Hy8tnTRm0xw/7464-IOPS,-capacity,-bandwidth-and-something-new-to-explain-to-the-people-in-purchasing.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7464-IOPS,-capacity,-bandwidth-and-something-new-to-explain-to-the-people-in-purchasing.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7464</wfw:comment>

    

    <author>nospam@example.com (Woo)</author>
    <content:encoded><![CDATA[
    Back at the time when we had 2/4/9gb SCSI drives, we didn't need the capacity either <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/wink.png" alt=";-)" style="display: inline; vertical-align: bottom;" class="emoticon" /><br />
at least not in the numbers we need it today.<br />
I recall when one of my former employees purchased an A1000 shelf with whopping ONE HUNDRED GIGABYTES! Who'd ever get that beast full?! And the lightning speed of.. what'd that thing run on.. 80MB/s?<br />
<br />
And then someone came and invented the internet... 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/Hy8tnTRm0xw" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sat, 26 May 2012 15:53:00 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7464-guid.html#c225838</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7464-IOPS,-capacity,-bandwidth-and-something-new-to-explain-to-the-people-in-purchasing.html#c225838</feedburner:origLink></item>
<item>
    <title>Woo: Nanosecond</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/QGCNKCiB6Xc/7468-Nanosecond.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7468-Nanosecond.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7468</wfw:comment>

    

    <author>nospam@example.com (Woo)</author>
    <content:encoded><![CDATA[
    I've been re-using her comparison many times already, when people complained that "the computer industry has stalled. we've seen 50% speed increases each year before, and now they're drumming along on their 3GHz for ages..."<br />
Showing someone that their 3GHz is actually just a few inches tends to open some eyes.<br />
<br />
The most eye-opening reply I got to that, was along the lines of "what's physics got to do with that? chips are electrical.".. some people are hard to convince that physics affects more than just moving parts. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/QGCNKCiB6Xc" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sat, 26 May 2012 15:22:22 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7468-guid.html#c225837</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7468-Nanosecond.html#c225837</feedburner:origLink></item>
<item>
    <title>Woo: Translations</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/EJVHxskAR6o/7466-Translations.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7466-Translations.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7466</wfw:comment>

    

    <author>nospam@example.com (Woo)</author>
    <content:encoded><![CDATA[
    On the other hand, using CPU sets or bindings severely impacts the total power that the process can use.. so while you may gain some speed from the reduced TLB cleanups, you probably limit your application from maximum performance in peak load situations.<br />
That's a tradeoff that needs to be carefully evaluated. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/EJVHxskAR6o" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sat, 26 May 2012 15:14:54 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7466-guid.html#c225836</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7466-Translations.html#c225836</feedburner:origLink></item>
<item>
    <title>Jason Ehrhart: Nanosecond</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/iTSjrIPdjvU/7468-Nanosecond.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7468-Nanosecond.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7468</wfw:comment>

    

    <author>nospam@example.com (Jason Ehrhart)</author>
    <content:encoded><![CDATA[
    She was great. <br />
<br />
I was fortunate enough to sit next to her for a cross country plane ride in the 1980s. I had already seen her once before and knew her nanosecond speak. She was very gracious and we discuss computers for several hours. Gave me a handful of "nanoseconds" before we got off the plane. <br />
<br />
This is why our approach of working on the hard part of the problem, the parallel processing part will ultimately pay off. <br />
<br />
Frequency is a dead end at some point and further gains in compute power will come from the easiest and best implemented parallel effort. Our method of matching software and hardware threads is the key to unlocking massively parallel computing. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/iTSjrIPdjvU" height="1" width="1"/>]]></content:encoded>

    <pubDate>Fri, 25 May 2012 00:26:32 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7468-guid.html#c225835</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7468-Nanosecond.html#c225835</feedburner:origLink></item>
<item>
    <title>Alan Hargreaves: Nanosecond</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/5v1zmrP6ssw/7468-Nanosecond.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7468-Nanosecond.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7468</wfw:comment>

    

    <author>nospam@example.com (Alan Hargreaves)</author>
    <content:encoded><![CDATA[
    I remember this being drummed into us during Digital Design at Uni. It's important to consider it when laying out PCB tracks.<br />
<br />
alan. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/5v1zmrP6ssw" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 23 May 2012 00:11:36 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7468-guid.html#c225834</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7468-Nanosecond.html#c225834</feedburner:origLink></item>
<item>
    <title>greg schulz: IOPS, capacity, bandwidth - and something new to explain to the people in purchasing</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/4huEwwCgSsA/7464-IOPS,-capacity,-bandwidth-and-something-new-to-explain-to-the-people-in-purchasing.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7464-IOPS,-capacity,-bandwidth-and-something-new-to-explain-to-the-people-in-purchasing.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7464</wfw:comment>

    

    <author>nospam@example.com (greg schulz)</author>
    <content:encoded><![CDATA[
    Hello Kevin, Im not surprised with what you are seeing or have seen when attaching a SSD to a USB2.0. USB3.0 helps improve, if you can go to eSATA even better, however for best performance, attach the SSD to an internal SATA port or if available SAS port.<br />
<br />
As you mentioned, IOPS should be much higher with USB3.0 vs. USB2.0 while latency is lower. Btw, what size IOs on average are you doing or seeing, along with are they reads or writes, random or sequential.<br />
<br />
As an FWIW/FYI, I attached one of my HHDDs that has 8GB slc nand flash/SSD built into the drive, attached it to a laptop via eSATA and then copied around 25GB in about 10 minutes. Not blazing fast and IOPS were bad as was latency during that time to those devices however bandwidth was impressive for eSATA/USB3.0 category. In other words an example of what happens to IOPS when bandwidth increases and vise versa.<br />
<br />
hope that helps<br />
gs 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/4huEwwCgSsA" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 21 May 2012 18:04:36 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7464-guid.html#c225831</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7464-IOPS,-capacity,-bandwidth-and-something-new-to-explain-to-the-people-in-purchasing.html#c225831</feedburner:origLink></item>
<item>
    <title>Kevin Allan: IOPS, capacity, bandwidth - and something new to explain to the people in purchasing</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/hwopFPFwJxg/7464-IOPS,-capacity,-bandwidth-and-something-new-to-explain-to-the-people-in-purchasing.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7464-IOPS,-capacity,-bandwidth-and-something-new-to-explain-to-the-people-in-purchasing.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7464</wfw:comment>

    

    <author>nospam@example.com (Kevin Allan)</author>
    <content:encoded><![CDATA[
    Hi Greg,<br />
<br />
With regards to IOPS I have seen terrible results using a 60GB SATA2 SSD with USB2.0 - USB2 really chokes it - IOPS and transfer speed suffer. Response time was over 10 SECONDS.<br />
<br />
However I thought I'd try a SATA3 SSD with USB3.0 and the speed is amazing. IOPS are through the roof and response time is nice and low.<br />
<br />
I'd be interested to know what figures you were getting.<br />
<br />
Thanks<br />
Kevin 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/hwopFPFwJxg" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 21 May 2012 04:44:37 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7464-guid.html#c225829</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7464-IOPS,-capacity,-bandwidth-and-something-new-to-explain-to-the-people-in-purchasing.html#c225829</feedburner:origLink></item>
<item>
    <title>Joerg M.: ZFS Dedup Internals</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/754QXnRBtPQ/7271-ZFS-Dedup-Internals.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7271-ZFS-Dedup-Internals.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7271</wfw:comment>

    

    <author>nospam@example.com (Joerg M.)</author>
    <content:encoded><![CDATA[
    There is no impact to boot/import times, as the DDT is loaded as needed ... so the pool is imported as fast as without dedup. At the end the DDT resides on disk. It's cached like normal metadata.<br />
<br />
Writing the DDT is part of the normal write process. However: Why <strong>must</strong> it be synced? Worst thing that can happen, when you loose some parts of the DDT table that you don't use the corresponding blocks for deduplication .... 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/754QXnRBtPQ" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sat, 19 May 2012 09:50:11 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7271-guid.html#c225828</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7271-ZFS-Dedup-Internals.html#c225828</feedburner:origLink></item>
<item>
    <title>Joerg+M.: Tracks</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/nli9QYfHxXM/7465-Tracks.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7465-Tracks.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7465</wfw:comment>

    

    <author>nospam@example.com (Joerg+M.)</author>
    <content:encoded><![CDATA[
    It was a c-polariation filter on the camera ... <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/smile.png" alt=":-)" style="display: inline; vertical-align: bottom;" class="emoticon" /> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/nli9QYfHxXM" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 16 May 2012 08:28:46 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7465-guid.html#c225814</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7465-Tracks.html#c225814</feedburner:origLink></item>
<item>
    <title>stu: Tracks</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/FJyvWk7GCa4/7465-Tracks.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7465-Tracks.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7465</wfw:comment>

    

    <author>nospam@example.com (stu)</author>
    <content:encoded><![CDATA[
    Very nice, I like the way the eye is taken right into the picture.  Did you use any filters not to make the green look so vibrant ? 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/FJyvWk7GCa4" height="1" width="1"/>]]></content:encoded>

    <pubDate>Tue, 15 May 2012 19:46:36 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7465-guid.html#c225813</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7465-Tracks.html#c225813</feedburner:origLink></item>
<item>
    <title>Tim Kennedy: ZFS Dedup Internals</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/dTpkpJ4ctGk/7271-ZFS-Dedup-Internals.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7271-ZFS-Dedup-Internals.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7271</wfw:comment>

    

    <author>nospam@example.com (Tim Kennedy)</author>
    <content:encoded><![CDATA[
    If the DDT is metadata, what impact is there to boot times, or zpool import times, when a large DDT must be loaded from disk to ARC/L2ARC?  What impacts are there to pool performance keeping the DDT synced to disk, as it must be, to provide consistency across reboots/outages? 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/dTpkpJ4ctGk" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 10 May 2012 23:27:27 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7271-guid.html#c225812</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7271-ZFS-Dedup-Internals.html#c225812</feedburner:origLink></item>
<item>
    <title>artodeto: Köhlbrand Bridge</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/BUkMZM0YYPM/7463-Koehlbrand-Bridge.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7463-Koehlbrand-Bridge.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7463</wfw:comment>

    

    <author>nospam@example.com (artodeto)</author>
    <content:encoded><![CDATA[
    I realy love the image.<br />
<br />
Thank you for the original size on flickr. I will add this as poster to my corridor (with your name attached). 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/BUkMZM0YYPM" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 07 May 2012 17:48:48 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7463-guid.html#c225803</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7463-Koehlbrand-Bridge.html#c225803</feedburner:origLink></item>
<item>
    <title>greg schulz: IOPS, capacity, bandwidth - and something new to explain to the people in purchasing</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/WPy16EeM8tg/7464-IOPS,-capacity,-bandwidth-and-something-new-to-explain-to-the-people-in-purchasing.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7464-IOPS,-capacity,-bandwidth-and-something-new-to-explain-to-the-people-in-purchasing.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7464</wfw:comment>

    

    <author>nospam@example.com (greg schulz)</author>
    <content:encoded><![CDATA[
    Hello Joerg,<br />
<br />
Nice post and you nailed it with there are more attributes for storage than capacity, particular IOPS and bandwidth which are starting to get more awareness and focus. All too often, those who do not know better look at storage on a cost per GByte/TByte basis without factoring in activity (e.g. performance) or availability. <br />
<br />
Thus bringing IOPS (activity) and bandwidth (ability to move data) is part of expanding the discussion and hopefully awareness. However also what needs to come into the discussion particular for databases is latency or response time. With SSDs, the good news is that many people are now starting to talk about and toss IOPS around, yet one of the key attributes of SSDs is ability to reduce response time or latency. Let us also revisit that as IOPS increase which is usually due to a smaller IO size, bandwidth will also increase however not at the same rate as if a larger IO size. In other words, many small IOPS will usually max out an interface, adapter, port, device before its full bandwidth (spec speed) is achieved. <br />
<br />
Likewise, fewer yet much larger IOPs can max out an interface, adapter, port, device bandwidth capabilities before its full IOP capabilities (spec speed) is achieved. As an example, look at some of the out of this world SSD benchmarks some vendors are touting where not tens of thousands of IOPS, rather hundreds of thousands of IOPS or more are touted. In some of those, that IOP size can be as low as 64 bytes or a fraction of a 512 byte (1/2 Kbyte ) page. Those kind of IOPs might impress however if focused on bandwidth, they would also disappoint, not to mention a 64 byte IO vs. a database IOP of 4K to 8K (e.g. 4,096 bytes to 8192 bytes) is not relative to most environments.<br />
<br />
Likewise, availability or accessibility is also important because without it, you do not have performance, or without performance, you do not have availability.<br />
<br />
I like your comment about purchasing or management or other informed focused on cost and capacity suggest a USB 1TB device. The reason I like that comment is a fun response would be to tell the bean counter to get rid of their computer and go back to a hand punched calculator adding machine as that too would allow them to get their job done. Granted the hand punched adding machine would not be as effective or productive, however it would sure cost a lot less.<br />
<br />
Now back to the USB SSD, Im assuming that is being used as an example, as other than some USB thumb drives, most if not all USB SSDs are actually SATA with a USB bridge. How do I know this? Simple, I have some of those and for fun (ok, geek fun) I have attached SATA SSDs using my bridge/connector cable to a USB 2 and USB 3 port and yes it limits IOPS as well as bandwidth and latency. Plug the same SSD into an eSATA (external SATA) port and all of the sudden the SSD starts to stretch its performance legs until the port/controller/server/system can no longer support it. Need even more performance, get a faster 6Gb/s SSD and attach it to a 6Gb/s wide SAS port (requires SAS adapter), or to a RAID card/adapter or controller that also supports caching.<br />
<br />
<br />
However availability comes back to the discussion in that with that much data on a device for something important, regardless of if HDD, HHDD or SSD, there should be at least two in a RAID 1 (mirror) or other RAID level for protection unless being replicated in real-time to another system.<br />
<br />
Need more performance than a single device or adapter or wide port can deliver (keep in mind wide sas is actually 6Gb/s x number of lanes, send/receive assuming the port and drive supports it)? Then get a faster device or use a PCIe cache or target card.<br />
<br />
However back to your points, look beyond the cost per GByte/TByte; look at productivity that means IOPS (including size, reads/writes), bandwidth (transfer), and latency as well as availability.<br />
<br />
Thus you nailed it with bringing IOPS and bandwidth into the discussion, now expand the discussion with latency, availability or HA. Also expand the IOP discussion to IO size, read/write, random and sequential along with how IOPSs and latency and bandwidth are all related.<br />
<br />
Cheers<br />
gs<br />
<br />
Greg Schulz - Sr. Advisory consultant StorageIO<br />
Author "Cloud and Virtual Data Storage Networking" (CRC Press) 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/WPy16EeM8tg" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sun, 29 Apr 2012 15:58:55 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7464-guid.html#c225797</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7464-IOPS,-capacity,-bandwidth-and-something-new-to-explain-to-the-people-in-purchasing.html#c225797</feedburner:origLink></item>
<item>
    <title>Joerg+M.: Swap</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/u053Btz4wzM/7462-Swap.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7462-Swap.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7462</wfw:comment>

    

    <author>nospam@example.com (Joerg+M.)</author>
    <content:encoded><![CDATA[
    I obviously delete entries, that comment in a generic manner, just linking to a website like "italy wine tours" or something like that ... like the article you are perhaps refering to ... the spam filtering is not perfect. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/u053Btz4wzM" height="1" width="1"/>]]></content:encoded>

    <pubDate>Fri, 27 Apr 2012 15:09:17 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7462-guid.html#c225794</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7462-Swap.html#c225794</feedburner:origLink></item>
<item>
    <title>Heretik: Swap</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/4UBqPXZKxMs/7462-Swap.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7462-Swap.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7462</wfw:comment>

    

    <author>nospam@example.com (Heretik)</author>
    <content:encoded><![CDATA[
    Is it just me or are comments »vanishing« from your blog? 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/4UBqPXZKxMs" height="1" width="1"/>]]></content:encoded>

    <pubDate>Fri, 27 Apr 2012 14:42:12 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7462-guid.html#c225793</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7462-Swap.html#c225793</feedburner:origLink></item>
<item>
    <title>JFPeng: Solaris 11 LKSF</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/r5nDD6hXc3s/7457-Solaris-11-LKSF.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7457-Solaris-11-LKSF.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7457</wfw:comment>

    

    <author>nospam@example.com (JFPeng)</author>
    <content:encoded><![CDATA[
    Congratulation, too!<br />
I have a little girl on Valentine's Day this year. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/r5nDD6hXc3s" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 26 Apr 2012 18:16:08 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7457-guid.html#c225791</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7457-Solaris-11-LKSF.html#c225791</feedburner:origLink></item>
<item>
    <title>arndt: Köhlbrand Bridge</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/abyLnm9zXRc/7463-Koehlbrand-Bridge.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7463-Koehlbrand-Bridge.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7463</wfw:comment>

    

    <author>nospam@example.com (arndt)</author>
    <content:encoded><![CDATA[
    cool.<br />
<br />
I will see it in nearly 4 weeks. <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/smile.png" alt=":-)" style="display: inline; vertical-align: bottom;" class="emoticon" /> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/abyLnm9zXRc" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 23 Apr 2012 11:50:20 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7463-guid.html#c225782</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7463-Koehlbrand-Bridge.html#c225782</feedburner:origLink></item>
<item>
    <title>Manuel Z: Swap</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/pewqUsHzpyY/7462-Swap.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7462-Swap.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7462</wfw:comment>

    

    <author>nospam@example.com (Manuel Z)</author>
    <content:encoded><![CDATA[
    Hi Jörg,<br />
<br />
thanks for bringing up the topic, what is your opinion on application independent monitoring of the swap utilization? I am unsure if we really need a generic swap utilization monitoring, but a lot of monitoring tools have it in there standard checks. E.g. Oracle Grid Control, which monitors oracle databases servers.<br />
	<br />
The "eager allocator" makes it very hard to define a generic swap utilization monitoring, or?<br />
<br />
The calculation with the "swap -s" values:  (used / (used+available) )  only makes sense, if:<br />
1. it's ok, if the application pages out to swap disks<br />
2. you configure swap-disk-space=physical mem.<br />
<br />
But for which applications does this fit? Are there any?<br />
<br />
Is the default Swap Utilization Metric  in Grid Control just wrong for typical database servers?<br />
------<br />
See: How GC Calculates Swap Utilization(%) Metric for Solaris Hosts [ID 1082352.1]<br />
...<br />
Output of 'swap -s' is:<br />
total: 2514952k bytes allocated + 202368k reserved = 2717320k used, 7021424k available<br />
<br />
Swap Utilization (%) is:<br />
(used / (used+available) ) * 100<br />
(2717320/(2717320+7021424))*100<br />
= 27.9%<br />
...<br />
------- 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/pewqUsHzpyY" height="1" width="1"/>]]></content:encoded>

    <pubDate>Fri, 20 Apr 2012 11:24:38 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7462-guid.html#c225770</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7462-Swap.html#c225770</feedburner:origLink></item>
<item>
    <title>Joerg M.: Swap</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/CSWnyPErVSI/7462-Swap.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7462-Swap.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7462</wfw:comment>

    

    <author>nospam@example.com (Joerg M.)</author>
    <content:encoded><![CDATA[
    2001 ... there are newer sources ...<br />
<br />
/onnv/onnv-gate/usr/src/cmd/swap/swap.c:<br />
at <a href="http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/swap/swap.c#303" target="_blank">http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/swap/swap.c#303</a><br />
    310 	/*<br />
    311 	 * max = total amount of swap space including physical memory<br />
    312 	 * ai.ani_max = MAX(anoninfo.ani_resv, anoninfo.ani_max) +<br />
    313 	 *	availrmem - swapfs_minfree;<br />
    314 	 * ai.ani_free = amount of unallocated anonymous memory<br />
    315 	 *	(ie. = resverved_unallocated + unreserved)<br />
    316 	 * ai.ani_free = anoninfo.ani_free + (availrmem - swapfs_minfree);<br />
    317 	 * ai.ani_resv = total amount of reserved anonymous memory<br />
    318 	 * ai.ani_resv = anoninfo.ani_resv;<br />
    319 	 *<br />
    320 	 * allocated = anon memory not free<br />
    321 	 * reserved = anon memory reserved but not allocated<br />
    322 	 * available = anon memory not reserved<br />
    323 	 */ 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/CSWnyPErVSI" height="1" width="1"/>]]></content:encoded>

    <pubDate>Fri, 20 Apr 2012 08:46:46 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7462-guid.html#c225769</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7462-Swap.html#c225769</feedburner:origLink></item>
<item>
    <title>InsideMan: Swap</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/__bfv5EZCZw/7462-Swap.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7462-Swap.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7462</wfw:comment>

    

    <author>nospam@example.com (InsideMan)</author>
    <content:encoded><![CDATA[
    How you should read swap -s according to Richard  McDougall &amp; Jim Mauro:<br />
<br />
"# swap -s<br />
total: 101456k bytes allocated + 12552k reserved = 114008k used, 597736k available<br />
<br />
should read:<br />
<br />
total: 101456k bytes unallocated + 12552k allocated = 114008k reserved, 597736k available"<br />
<br />
See Solaris Internals<br />
Kernel Architecture &amp; Implementation<br />
26 June 2001 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/__bfv5EZCZw" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 19 Apr 2012 19:13:59 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7462-guid.html#c225767</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7462-Swap.html#c225767</feedburner:origLink></item>
<item>
    <title>Joerg M.: Swap</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/pxYq1PVGwQ0/7462-Swap.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7462-Swap.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7462</wfw:comment>

    

    <author>nospam@example.com (Joerg M.)</author>
    <content:encoded><![CDATA[
    Sorry, but that one is really simple. And many people know what it means.  You need really basic knowledge about the VM system in Solaris. You have to keep in mind that Solaris is an eager allocator. Thus as soon as you alloc memory in your app, swap space is reserved, however the allocation of swap space takes only place when you really need the swap pages. Thus the used amount of swap is the amount of allocated (used swap) and reserved swap (swap that is reserved, but not allocated so far). available should be obvious. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/pxYq1PVGwQ0" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 19 Apr 2012 17:59:47 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7462-guid.html#c225766</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7462-Swap.html#c225766</feedburner:origLink></item>
<item>
    <title>DontSwapMeOut: Swap</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/GrZ1yrKAEsU/7462-Swap.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7462-Swap.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7462</wfw:comment>

    

    <author>nospam@example.com (DontSwapMeOut)</author>
    <content:encoded><![CDATA[
    Solaris swap is still an area that needs clarification.<br />
<br />
Who knows what this means:<br />
<br />
# swap -s<br />
total: 24207752k bytes allocated + 1210144k reserved = 25417896k used, 104451256k available<br />
<br />
Nobody.<br />
<br />
Solaris memory/swap usage is still mystical and I know people who say the only meaningful number they look at is vmstat 's »sr« field. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/GrZ1yrKAEsU" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 19 Apr 2012 16:49:35 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7462-guid.html#c225765</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7462-Swap.html#c225765</feedburner:origLink></item>
<item>
    <title>Joerg M.: River</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/rIgmCzyirXM/7461-River.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7461-River.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7461</wfw:comment>

    

    <author>nospam@example.com (Joerg M.)</author>
    <content:encoded><![CDATA[
    Yup <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/smile.png" alt=":-)" style="display: inline; vertical-align: bottom;" class="emoticon" /> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/rIgmCzyirXM" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 19 Apr 2012 15:33:00 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7461-guid.html#c225764</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7461-River.html#c225764</feedburner:origLink></item>
<item>
    <title>Christian: River</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/Rs269_R5F88/7461-River.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7461-River.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7461</wfw:comment>

    

    <author>nospam@example.com (Christian)</author>
    <content:encoded><![CDATA[
    Die Ilmenau? 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/Rs269_R5F88" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 19 Apr 2012 13:37:56 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7461-guid.html#c225763</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7461-River.html#c225763</feedburner:origLink></item>
<item>
    <title>Mike: Swap</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/aaLIRVghLJs/7462-Swap.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7462-Swap.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7462</wfw:comment>

    

    <author>nospam@example.com (Mike)</author>
    <content:encoded><![CDATA[
    "It depends"? 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/aaLIRVghLJs" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 19 Apr 2012 06:33:51 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7462-guid.html#c225762</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7462-Swap.html#c225762</feedburner:origLink></item>
<item>
    <title>ajmaidak: Swap</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/lpoTvzA4DAU/7462-Swap.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7462-Swap.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7462</wfw:comment>

    

    <author>nospam@example.com (ajmaidak)</author>
    <content:encoded><![CDATA[
    As big as it needs to be isn't adequate? <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/smile.png" alt=":-)" style="display: inline; vertical-align: bottom;" class="emoticon" /> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/lpoTvzA4DAU" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 18 Apr 2012 15:51:28 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7462-guid.html#c225761</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7462-Swap.html#c225761</feedburner:origLink></item>
<item>
    <title>A Mellor: Swap</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/6xGS5OL6aww/7462-Swap.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7462-Swap.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7462</wfw:comment>

    

    <author>nospam@example.com (A Mellor)</author>
    <content:encoded><![CDATA[
    Looking forward to reading your thoughts on this difficult topic 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/6xGS5OL6aww" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 18 Apr 2012 10:20:13 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7462-guid.html#c225760</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7462-Swap.html#c225760</feedburner:origLink></item>
<item>
    <title>Joerg M.: Performance impact of Zones.</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/A2sXj_bvZy8/7455-Performance-impact-of-Zones..html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7455-Performance-impact-of-Zones..html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7455</wfw:comment>

    

    <author>nospam@example.com (Joerg M.)</author>
    <content:encoded><![CDATA[
    You can use a custom site.xml for this ... i used something like that for my Crossbow tutorial <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/smile.png" alt=":-)" style="display: inline; vertical-align: bottom;" class="emoticon" /> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/A2sXj_bvZy8" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 16 Apr 2012 09:28:18 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7455-guid.html#c225746</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7455-Performance-impact-of-Zones..html#c225746</feedburner:origLink></item>
<item>
    <title>Woo: Performance impact of Zones.</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/RjjeTSGzduE/7455-Performance-impact-of-Zones..html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7455-Performance-impact-of-Zones..html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7455</wfw:comment>

    

    <author>nospam@example.com (Woo)</author>
    <content:encoded><![CDATA[
    only partially relevant to the topic: do you happen to have any hints on how to define (in Solaris 10) which services are supposed to be running in a newly installed zone?<br />
We're creating zones by the dozen on our servers, and the first thing after a zone install, is running a script that disables all the default useless and/or dangerous services (Gnome login, X font server, IPP, Webconsole, telnet etc...).<br />
Is there any simple way to either specify a service set to be set, or an option to inherit the SMF repository from the global zone? (short of cloning a template zone, which brings its own implications and is undesirable in this regard). 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/RjjeTSGzduE" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 16 Apr 2012 02:45:29 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7455-guid.html#c225745</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7455-Performance-impact-of-Zones..html#c225745</feedburner:origLink></item>
<item>
    <title>Joerg+M.: Solaris 11 LKSF</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0orgKommentare/~3/cWI1gb2B-JQ/7457-Solaris-11-LKSF.html</link>
            <category />
    
    <comments>http://www.c0t0d0s0.org/archives/7457-Solaris-11-LKSF.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7457</wfw:comment>

    

    <author>nospam@example.com (Joerg+M.)</author>
    <content:encoded><![CDATA[
    Congratulation! <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/smile.png" alt=":-)" style="display: inline; vertical-align: bottom;" class="emoticon" /> Hope your wife and your baby is all well! <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/smile.png" alt=":-)" style="display: inline; vertical-align: bottom;" class="emoticon" /> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0orgKommentare/~4/cWI1gb2B-JQ" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sat, 14 Apr 2012 11:03:57 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7457-guid.html#c225728</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7457-Solaris-11-LKSF.html#c225728</feedburner:origLink></item>

</channel>
</rss>

