{"id":108,"date":"2010-04-08T08:02:55","date_gmt":"2010-04-08T14:02:55","guid":{"rendered":"http:\/\/www.unifiedcomputingblog.com\/?p=108"},"modified":"2010-04-08T08:02:55","modified_gmt":"2010-04-08T14:02:55","slug":"8gb-fibre-channel-or-10gb-ethernet-w-fcoe","status":"publish","type":"post","link":"http:\/\/www.unifiedcomputingblog.com\/?p=108","title":{"rendered":"8Gb Fibre Channel or 10Gb Ethernet w\/ FCoE?"},"content":{"rendered":"

Update 2011\/01\/31 – I’ve added new thoughts and comments on the subject here: http:\/\/www.unifiedcomputingblog.com\/?p=234<\/a><\/p>\n

Which is better?\u00a0\u00a0 Which is faster?<\/p>\n

I’ve been stuck on this one for a while.\u00a0\u00a0 I’m traditionally a pure fibre channel kind of guy, so I’ve been pretty convinced that traditional FC was here to stay for a while, and that FCoE – as much as I believe in the technology – would probably be limited to the access and aggregation layers for the near term.\u00a0\u00a0 That is, until it was pointed out to me the encoding mechanisms used by these two technologies and the effective data rates they allowed.\u00a0\u00a0 I’m not sure why it never occurred to me before, but it hit me like the proverbial ton of bricks this week.<\/p>\n

First off, a quick review of encoding mechanisms.\u00a0\u00a0 Any time we’re transmitting or storing data, we encode it in some form or another.\u00a0\u00a0 Generally, this is to include some type of a checksum to ensure that we can detect errors in reading or receiving the data.\u00a0\u00a0 I remember the good old days when I discovered that RLL hard drive encoding was 50% more efficient than MFM encoding, and with just a new controller and a low level format, my old 10MB (yes, that’s ten whopping megabytes, kids.\u00a0\u00a0 Ask your parents what a megabyte was.)\u00a0 suddenly became 15MB!\u00a0\u00a0 Well, we’re about to embark on a similar discovery.<\/p>\n

1, 2, 4, and 8 Gb Fibre Channel all use 8b\/10b encoding.\u00a0\u00a0 Meaning, 8 bits of data gets encoded into 10 bits of transmitted information – the two bits are used for data integrity.\u00a0\u00a0 Well, if the link is 8Gb, how much do we actually get to use for data – given that 2 out of every 10 bits aren’t “user” data?\u00a0\u00a0 FC link speeds are somewhat of an anomaly, given that they’re actually faster than the stated link speed would suggest.\u00a0\u00a0 Original 1Gb FC is actually 1.0625Gb\/s, and each generation has kept this standard and multiplied it.\u00a0 8Gb FC would be 8×1.0625, or actual bandwidth of 8.5Gb\/s.\u00a0\u00a0 8.5*.80 = 6.8.\u00a0\u00a0 6.8Gb of usable bandwidth on an 8Gb FC link.<\/p>\n

10GE (and 10G FC, for that matter) uses 64b\/66b encoding.\u00a0\u00a0 For every 64 bits of data, only 2 bits are used for integrity checks.\u00a0\u00a0 While theoretically this lowers the overall protection of the data, and increases the amount of data discarded in case of failure, that actual number of data units that are discarded due to failing serialization\/deserialization is minuscule.\u00a0\u00a0\u00a0 For a 10Gb link using 64b\/66b encoding, that leaves 96.96% of the bandwidth for user data, or 9.7Gb\/s.<\/p>\n

So 8Gb FC = 6.8Gb usable, while 10Gb Ethernet = 9.7Gb usable.\u00a0\u00a0 Even if I was able to use all of the bandwidth available on an 8Gb FC port (which is very unlikely at the server access layer), with 10GE running FCoE, I’d still have room for 3 gigabit Ethernet-class “lanes”.\u00a0\u00a0 How’s that for consolidation?<\/p>\n

10Gb FC has the same usable bandwidth, and without the overhead (albeit a small 2% or so) of FCoE, but you don’t get the consolidation benefits of using the same physical link for your storage and traditional Ethernet traffic.<\/p>\n

I’m sold.<\/p>\n","protected":false},"excerpt":{"rendered":"

Update 2011\/01\/31 – I’ve added new thoughts and comments on the subject here: http:\/\/www.unifiedcomputingblog.com\/?p=234 Which is better?\u00a0\u00a0 Which is faster? I’ve been stuck on this one for a while.\u00a0\u00a0 I’m traditionally a pure fibre channel kind of guy, so I’ve been pretty convinced that traditional FC was here to stay for a while, and that … Continue reading 8Gb Fibre Channel or 10Gb Ethernet w\/ FCoE?<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[5],"tags":[19,23],"class_list":["post-108","post","type-post","status-publish","format-standard","hentry","category-miscellaneous","tag-dcb","tag-fcoe"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=\/wp\/v2\/posts\/108","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=108"}],"version-history":[{"count":0,"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=\/wp\/v2\/posts\/108\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=108"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=108"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=108"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}