3 ms·
"There are whole categories of problems that are pleasantly parallel, and in those cases the [Linpack maximum] number is really not as important because we did
by ChuckMcM 13y ago
"There are whole categories of problems that are pleasantly parallel, and in those cases the [Linpack maximum] number is really not as important because we did intentionally make use of the entire 1.2 petaflops because they were all concurrently executing the workloads," Stowe told Ars. "Maybe there does need to be a different metric for analytics and big data and genomics—and all these pleasantly parallel workloads that are becoming more pervasive."
I wonder if people miss this part. For easily parallel projects, Amazon is great since any core can make progress regardless of the other cores state or reachability. But if there is any inter-dependence between the cores (I use the term engtangling but others have called it co-dependence) the number becomes limited by the bisection bandwidth between cores. Poorly scheduled (like randomly scheduling on a core) is the worst case, if you can keep the bandwidth between entangled cores high, even if the system bandwidth is low, you can improve things (dramatically some times). But at the end of the day its the level of sharing between cores that will tell you if you can do your problem in the 'cloud' or if you are going to need a local data center.
- deleted 13y ago[deleted]