Comments on: Microsoft Azure Goes Back To Rack Servers With Project Olympus https://www.nextplatform.com/2016/11/01/microsoft-azure-goes-back-rack-servers-project-olympus/ In-depth coverage of high-end computing at large enterprises, supercomputing centers, hyperscale data centers, and public clouds. Mon, 23 Apr 2018 11:17:27 +0000 hourly 1 https://wordpress.org/?v=6.7.1 By: Kerry Main https://www.nextplatform.com/2016/11/01/microsoft-azure-goes-back-rack-servers-project-olympus/#comment-72427 Mon, 07 Nov 2016 03:47:19 +0000 http://www.nextplatform.com/?p=4838#comment-72427 A fundamental flaw in the cheap rack server model is that while cpu, cache, memory and flash storage technologies have increased exponentially in the last 10 years, local LAN network latency (TCPIP stack, NIC buffers, router hops, firewalls, load balancer times etc) has not improved at all.

Next generation compute models need to handle extreme amounts of data which means getting data closer to the compute engine in much shorter time-frames.

In relative terms, cpu-cache,cpu-memory, cpu-flash storage can be measured in secs/mins/days whereas network write / replication updates (as in N-Tier models with lots of small systems) can be measured in months.

Even if cheaper and more available, how does one reconcile using rack models with the above when the over-riding goal is to reduce overall solution latency?

We are at the beginning of network tier consolidation whereby next generation models will be based on fewer, but much larger blade type servers (TB’s non-volatile local memory) that utilize high speed interconnects (e.g. CAPI, RoCEv2, others) e.g. clusters of big systems.

]]>