> On Mar 14, 2016, at 13:55, Lux, Jim (337C) <james.p....@jpl.nasa.gov> wrote: > > … And communication, even between nodes of a cluster, isn’t free, nor > infinitely scalable. I think that with a lot of problems, it’s the > communication bottleneck that is the “rate limiting” step, whether it’s > CPU:cache; CPU:RAM; or node:node communications. ...
Henry Neeman calls this the tyranny of the memory hierarchy and focuses on it quite heavily in his Supercomputing in Plain English series. My experiences benchmarking and tuning scientific software has borne this out many times over the years. charlie _______________________________________________ Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf