I didn&#x27;t know about it. Thanks for mention. My baseline for this topic of SOC&#x27;s w&#x2F; offloading is Cavium&#x27;s Octeon line:<p><a href="http:&#x2F;&#x2F;www.cavium.com&#x2F;OCTEON-III_CN7XXX.html" rel="nofollow">http:&#x2F;&#x2F;www.cavium.com&#x2F;OCTEON-III_CN7XXX.html</a><p>The summary should give you an idea. Just offloading TCP&#x2F;IP or filesystem ops by itself can knock a host CPU down from 90+% utilization to closer to 10%. That leaves a lot of room for compute. Such a situation helps whether the Octeon was the host or a coprocessor for a Xeon host. Now, apply that same principle to text algorithms, concurrency support, compression, SSL, Hadoop&#x27;s main ops, key mechanisms of deep learning, and so forth. Performance you get per dollar and watt gets crazy.<p>The only strategy I had that could deliver better was integrating FPGA&#x27;s with CPU&#x27;s so workload could be split. Intel is already on top of that with Altera acquisition. I can&#x27;t wait to see accelerator logic on a Xeon. :) Meanwhile, a combo of multicore CPU and libraries that tap into accelerators is much easier for average developer to use. No hardware design experience necessary.