lun, 15 Feb 2010, Devon McCormick skribis: > Raul - yes - there's always been a lot of hand-waving magic about the > benefits of parallel processing but many a pretty ship of theory has > foundered on the cold hard rocks of fact. Until you consider a specific > problem and do the work, you can't make any claims about the benefits. > > In fact, it's easy to offer a "dis-proof of concept": parallelize > > 1 2+3 4 > > I bet any parallel version of this will lose to the non-parallel version - > there's no way the overhead cost of breaking up and re-assembling the > results of this small piece of work is less than simply doing it.
I agree with you. Given the large memory cache available in modern computer, it is better to just keep memory reference locality. The speed of transfer of data using socket would be slower than that within cache by at least 2 order of magnitude, just wild guess. I did writing a J web server that initialize a new Jconsole instance to serve in-coming calls from each client, and that make a good job to distribute loading to each cpu core, but I wouldn't say that is a parallel program, just trivial cgi programming. -- regards, ==================================================== GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
