News for hackers. Stuff that matters.
Re:Multi-core and multi-threading performance by jbooth on Thursday October 11, 2012 @10:44AM (#4640974)
You've still got a driver program that coordinates the massively parallel stages, most likely, and a less-scalable dispatch process where not all nodes are yet doing work.
Re:Multi-core and multi-threading performance by CookWithMe on Thursday October 11, 2012 @11:25AM (#4641177)
Yes, there definitely are programs where this holds true (as I have said), but there are others where it does not. A simple, but perfectly reasonable example is brute-force search for cracking a password (if you got the hash of the password). Your dispatch is simple: send every node 1) the hash, 2) the number of nodes, 3) it's own number. With 2) and 3), each node can easily figure out where it starts. You need no more communication until one of the nodes finds the password.

See https://en.wikipedia.org/wiki/Embarrassingly_parallel

Again, you said "most parallel", and not "average parallel", and this is what I have commented on.