Once again it's Tuesday, which means IBM announcement day!
Today IBM announced [two new DS3400 SAN Express Models]. These two new models will replace the IBM System Storage DS3400 SAN Express Kit model 41U and 42U to be withdrawn from marketing today. The DS3000 series of scalable, flexible, and affordable storage solutions support IBM System x, System p, and BladeCenter servers.
Two new IBM System Storage DS3400 SAN Express Kits are being introduced that provide the parts needed to setup and configure a SAN with the exception of a SAN switch that can be ordered separately. The IBM System Storage DS3400 SAN Express Kits contain Emulex EZPilot software that enables automated installation and configuration of the SAN components. IBM System Storage DS3400 SAN Express Kits models 41S and 42S and Emulex EZPilot software work in conjunction with the IBM TotalStorage SAN16B-2 Express Model Switch which comes with eight ports and eight 4 Gbps SFPs. The EZPilot software can support configurations with either one or two SAN16B-2 switches.
The 41S is a single-controller model DS3400 with two HBA cards and four cables. The 42S is the dual-controller model with two HBA cards and eight cables.Read More]
Network Products Guide has two of my favorite IBM products up for "Best Product of 2008" awards.
IBM System Storage SAN Volume Controller is up for:
IBM System z10 Enterprise Class mainframe server is up for:
If you'd like to put in your vote, go to their virtual[Voting Booth].Read More]
Thirteen months ago, fellow IBM blogger Bob Sutor suggested the potential for avatars to [move from one virtual world to another].I thought this was far, far in the future myself, but this week, IBM and Linden Labs, the makersof Second Life, successfully teleported an avatar from SecondLife over to OpenSim. Here is the[Press Release].
If you are thinking there is no business value here, consider that Cisco has this incredible [11-minute demonstration video] that haspresenters in one city on the stage at another city.
Well, my job is done here in Tokyo, and my team is off next to Mumbai, India. This of course will takethe bulk of tomorrow in airplanes and airports, and not be as easy as teleporting in the metaverse!Read More]
Continuing my week in Tokyo, Japan, I was going to title this post "Chunks, Extents and Grains", but decidedinstead to use the fairy tale above.
Fellow blogger BarryB from EMC, on his The Storage Anarchist blog, once again shows off his [PhotoShop talents], in his post [the laurel and hardy of thin provisioning]. This time, BarryB depicts fellow blogger and IBM master inventor, Barry Whyte, as Stan Laurel and fellow blogger Hu Yoshida from HDS as Oliver Hardy.
At stake is the comparison in various implementations of thin provisioning among the major storage vendors.On the "thick end", Hu presents his case for 42MB chunks on his post [When is Thin Provisioning Too Thin]. On the "thin end", IBMer BarryW presents the "fine-grained" details of Space-efficient Volumes (SEV), made available with the IBM System Storage SAN Volume Controller (SVC) v4.3, in his series of posts:
BarryB paints both implementations as "extremes" in inefficiency. Some excerpts from his post:
"... Hitachi's "chubby" provisioning is probably more performance efficient with external storage than is the SVC's "thin" approach. But it is still horribly inefficient in context of capacity utilization.
BarryB would like you to think that since EMC has chosen an "extent" size between 257KB and 41MB it must therefore be the optimal setting, not too hot, and not too cold. As I mentioned last January in my post[DoesSize Really Matter for Performance?], EMC engineers had not yet decided what that extent size should be, andBarryB is noticeably vague on the current value.According to this [VMware whitepaper],the thin extent size is currently 768 KBin size. Future versions of the EMC Enginuity operating environment may change the thin extent size. (I am sure theEMC engineers are smarter and more decisive than BarryB would lead us to believe!)
BarryB is correct that any thin provisioning implementation is not "free", even though IBM's implementation is offeredat no additional charge. Some writes may be slowed downwaiting for additional storage to be allocated to satisfy the request, and some amount of storage must be set asideto hold the metadata directory to point to all these chunks, extents or grains. For the convenience of not havingto dynamically expand LUNs manually as more space is needed, you will pay both a performance and capacity "price".
However, as they say, the [proof of the pudding is in the eating], or perhaps I should say porridge in this case.Given that the DMX4 is slower than both HDS USP-V and IBM SVC, you won't see EMC publishing indu So if you are a client waiting for your EMC equipment to be fully depreciated so you can replace it for faster equipment from IBM or HDS, you can at least improveits performance and capacity utilization today by virtualizing it with IBM SAN Volume Controller. technorati tags: Goldilocks, Three Bears, IBM, Tokyo, Japan, EMC, BarryB, PhotoShop, Barry Whyte, HDS, Hu Yoshida, USP-V, SVC, SEV, Stan Laurel, Oliver Hardy, Symmetrix, DMX4, metadata, directory, SPC, benchmarks
So if you are a client waiting for your EMC equipment to be fully depreciated so you can replace it for faster equipment from IBM or HDS, you can at least improveits performance and capacity utilization today by virtualizing it with IBM SAN Volume Controller.
technorati tags: Goldilocks, Three Bears, IBM, Tokyo, Japan, EMC, BarryB, PhotoShop, Barry Whyte, HDS, Hu Yoshida, USP-V, SVC, SEV, Stan Laurel, Oliver Hardy, Symmetrix, DMX4, metadata, directory, SPC, benchmarks[Read More]