Companies in several industries plan to take advantage of the new Intel Xeon Processor (News - Alert) E5-2600 family, according to a new survey focused on the adoption of the platform from telecom platform deployment solutions provider NEI (News - Alert).
Among the key markets, storage and security are leading the transition towards the Intel Xeon Processor E5-2600 Family of processors. In fact, the survey indicates that one third of all respondents plan to migrate to the Intel (News - Alert) Xeon Processor E5-2600 Family within the next 12 months.
To be precise, 40 percent of storage companies, 36 percent in the security industry, 35 percent in telecom and 23 percent in network management verticals plan to begin leveraging the Intel Xeon Processor E5-2600 Family in the next 12 months.
Further, the survey reveals that 68 percent of security companies will be using the E5-2600 Family within the next two years, followed closely by 60 percent in the storage market, 58 percent in telecom and 44 percent in network management.
NEI facilitates security, storage and telecom platform deployment among enterprises by offering the hardware, operating system and system management integration capabilities on a global basis to assist software developers in efficiently bringing solutions to market.
The company’s team of application engineering experts assists clients in the migration to
Intel’s Xeon E5-2600 processor family and its feature-rich values. The company provides the necessary support in the form of comprehensive validation and optimization services to ensure a smooth migration to this and future Xeon processor upgrades.
Key benefits of Xeon E5-2600 as perceived by the survey participants include dramatic performance increases, improved memory access and speed, greater power efficiency, stepped-up bandwidth increases, and increased data and infrastructure security.
However, there are some concerns that have arisen with the Intel Xeon E5-2600 family including the costs and resources to implement it, including tests and evaluation. However, there were fewer concerns with the potential of significant application rewrite/revisions and incompatibility with existing compilers, libraries, and profiler tools.
Edited by Jamie Epstein