I’m very pleased to welcome a new member to the Cisco USNIC/MPI Team: Dave Goodell. Welcome, Dave! (today was his first day)
In a prior blog post, I talked about latency analogies. I compared levels of latencies to your home, your neighborhood, a far-away neighborhood, and another city. I talked about these localities in terms of communication.
Let’s extend that analogy to talk about data locality.
The Cisco and Microsoft joint Cross-Animal Technology Project, a well-established player in the field of multi-species collaborative initiatives, is pleased to introduce its next project: a revolution in High Performance Computing (HPC): LOLCODE language bindings for the Message Passing Interface (MPI).
CATP believes that cats are natural predatory programmers. Who better to take advantage of all the world’s spare, unused computing cycles than cats? They’re at home when we’re not. They’re clever, they can problem-solve, and they have lots of free time on their… paws.
Multiple readers have told me that it is difficult for them to understand and/or visualize the effects of latency on their HPC applications, particularly in modern NUMA (non-uniform memory access) and NUNA (non-uniform network access) environments.
Let’s breaks down the different levels of latency in a typical modern server and network computing environments.
A number of you complained when blogs.cisco.com switched to requiring a social medial login to leave comments.
It turns out that you were not alone.
Industry-wide, it seems that many people do not want to associate their personal Facebook/Twitter/etc. logins with work-related social media (i.e., this effect was seen at more than just Cisco). The social media gurus here at Cisco have therefore dropped the social media login requirement in order to leave comments on Cisco blogs.
You can now leave blog comments in the same way you used to — just provide your name and email address.