Split up your jobs how? Is the job embarrassingly parallel? Because if it isn't, and most things aren't, it's going to require significant programmer overhead t

Split up your jobs how? Is the job embarrassingly parallel? Because if it isn't, and most things aren't, it's going to require significant programmer overhead to simply "split up your jobs". And then once you've split up the job, the different portions are going to need to exchange their in-progress results, because most real scientific computing programs involve iterating until either a certain number of timesteps have passed or a certain residual is reached. I mean, I only write HPC programming frameworks for scientific computing as my job, what do I know. But if you're doing anything more complex than map-reduce, a high-speed interconnect is essential, and even in mapreduce it's pretty handy.