siliconindia | | June 201619Mohan SankararamanCXO INSIGHTSDEVELOPING RIGHT TECHNICAL CAPABILITY FOR DIFFERENTIATED CUSTOMER EXPERIENCE Mohan Sankararaman, SVP, Deputy CIO, First Horizon National Corporation>The transition of HPC into the enterprise continues to face challenges, but not for reasonsyou might suspect. A legacy computing mindset, cost structures, and infrastructure issues have largely shouldered a majority of the blame for full adoption of HPC into the enterprise, but the reality is that the network itself is the bottleneck. In order for HPC to fully grow into an enterprise-ready play, existing Ethernet-based network attached storage needs an adjustment and I'd argue that the adjustment is already available­parallel file systems. The problem right now is that parallel file systems, especially Lustre, are largely misunderstood in the enterprise and therefore the current adoption rate is very low. According to Intersect360 industry analyst Addison Snell, "Lustre is still deployed by only about one-tenth of companies with high-performance or big data workloads."I believe that will change, and quickly. Customers on the enterprise level increasingly need storage platforms that optimize traffic from applications to the storage layer, featuring interoperability and support for complex and multi-protocol networks, and especially with the growth of Big Data. And they need hardware and customized software defined storage platforms that can help them scale quickly. In fact, I believe that Big Data initiatives and the need for scalability will be the driving forces behind the enterprises fully adopting Lustre. A parallel file system easily performs the feats mentioned above, and Lustre's list of benefits includes the following:· Highly scalable storage platform that can absorb almost any type of data influx· Stores application data persistently· Provides global shared namespace (files, directories)· Designed for high performance and to operate over high speed networks (IB, Myrinet, Portals) and optimized for I/O path for maximum bandwidth
< Page 9 | Page 11 >