Why is it called embarrasingly? What's the reasoning behind the word use? —The preceding unsigned comment was added by 69.25.246.40 (talk • contribs) 17:44
This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:
This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
This article is within the scope of WikiProject Mathematics, a collaborative effort to improve the coverage of mathematics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.MathematicsWikipedia:WikiProject MathematicsTemplate:WikiProject Mathematicsmathematics
This article is within the scope of WikiProject Engineering, a collaborative effort to improve the coverage of engineering on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.EngineeringWikipedia:WikiProject EngineeringTemplate:WikiProject EngineeringEngineering
Latest comment: 12 years ago6 comments6 people in discussion
Why is it called embarrasingly? What's the reasoning behind the word use? —The preceding unsigned comment was added by 69.25.246.40 (talk • contribs) 17:44, 23 June 2005 (UTC)
Maybe it's started as a criticism on a particular problem that might have been used as a benchmark. This is just second-guessing tho. As massively parallel tasks are the easiest to parallelizize (by definition), it doesn't get much respect from anyone if you have a computer that's capable of doing that. 62.220.237.6613:30, 23 April 2006 (UTC)Reply
Probably because it refers to problems that are so easy to parallelize, that it would be very embarrassing if your parallel computing system failed to do so. Compare "embarrassingly obvious". --Piet Delport18:25, 27 September 2006 (UTC)Reply
Agree with Piet Delport. In general, parallelizing algorithms is difficult. The difference between "embarassingly parallel" and "normally parallel" is analogous to trying to coordinate a team of cooks to each produce one single food dish, compared with using the same team for the same task where each cook must contribute to each dish. The former is embarassingly parallel. The latter is not, and is very much less efficient. Markjamesabraham (talk) 15:44, 4 May 2010 (UTC)Reply
Could you say that an "embarrassingly parallel" problem is one so trivial to parallelize that afterwards you feel embarrassed (or at least a bit silly) for thinking that it was a problem in the first place? "I've parallelized that algorithm! In other news, I tied my own shoelaces!" —Preceding unsigned comment added by 122.57.195.229 (talk) 10:43, 26 December 2010 (UTC)Reply
Or, alternatively, it's when the problem is so simple that it feels as though it was deliberately set up to be easy - like suddenly finding yourself with dozens of fawning servants doing for you even though you feel you've done nothing to deserve them.
This section of the "Talk:" page was interesting and helpful. Should there perhaps be a "section" in the actual article, that includes some of this information? Perhaps called (something like) "== Etymology of the term =="? Or should there perhaps be an article (maybe in Wiktionary?) called Etymology of the term "embarrassingly parallel"? -- (and maybe this article could "link" to it, or point to it)? Just an idea... Of course, in a talk page, the rules about "original research" and "blatant speculation" are not as strict; would this be a problem? ...and if so, then, could the new section (or, new article) "refer" readers to this section of the talk page? --Mike Schwartz (talk) 17:54, 21 February 2011 (UTC)Reply
Latest comment: 20 years ago1 comment1 person in discussion
I'm not sure I agree that game-tree search in artificial intelligence is in general (or even frequently) embarassingly parallel; while minimax is, alpha-beta is definitely not.
--Kenta212:30, 27 December 2005 (UTC)Reply
You are correct. Only the simplest implementations are. Any technique which uses gathered knowledge to search more effectively presets parallelistation problems. (Alpha-beta is an example). —The preceding unsigned comment was added by 84.193.175.91 (talk • contribs) 10:46, 12 January 2006 (UTC)
Pleasingly Parallel
Latest comment: 12 years ago3 comments3 people in discussion
The term doesn't mean that it's easy or trivial to parallelize something, just that it parallelizes nicely and provides large gains in speed. Something could be embarrassingly/pleasingly parallel but still be a nightmare to implement. --Bigpeteb (talk) 21:53, 27 February 2014 (UTC)Reply
Counter Examples
Latest comment: 4 years ago1 comment1 person in discussion
I believe this term is also used to describe cloud computing, as in, cloud computing is useful to solve embarassingly parallel problems like millions of users requesting search. But it would be helpful here to have some counter examples...what are examples of parallel computing at the other end of the spectrum from this?
Perhaps large and deep neural networks. The high connectivity between and within layers means tranches of neurons can't be separated and run independently from each other however much they are running "in parallel". — Preceding unsigned comment added by 125.238.199.71 (talk) 00:05, 27 June 2022 (UTC)Reply
Disconcertingly serial
Latest comment: 17 years ago1 comment1 person in discussion
The phrase "disconcertingly serial" has three matches on Google, none of which are relevant. This should not be included as if it were standard terminology. —Preceding unsigned comment added by 125.238.28.39 (talk) 11:01, 5 October 2008 (UTC)Reply
Two or more types of embarrassing parallelism?
Latest comment: 17 years ago1 comment1 person in discussion
Is there any mention in the literature for two or more types of embarrassing parallelism? I ask because although calculation of say... the Mandelbrot appears perfectly suited to the task, there is the factor that some pixels take many more times longer to calculate than other pixels. We're talking not just an offset of time, but a multiple.
This is a common issue in "pleasantly" parallel computing and is related to the halting problem.
But the point is that none of the other pixels have to wait for the laggards before they get their turn at being rendered. (While you could interleave iterations for different pixels, that leads to its own host of problems with things like locality.) While the previous commenter notes that this does relate to the Halting Problem, it's hardly limited to "'pleasantly' parallel computing": if one of your Mandelbrot set pixels takes n times longer to calculate than another then it's going to take n times longer to calculate whether you calculate them in parallel or not (as the page notes, cf. Amdahl's Law).
How are simulation problems embarrassingly parallel?
Latest comment: 17 years ago1 comment1 person in discussion
Latest comment: 15 years ago2 comments2 people in discussion
Thought it might be a good contribution if there was reference for major implementations of Parallel processing for various languages. What do you think? Talgalili (talk) 12:18, 30 August 2009 (UTC)Reply
Latest comment: 14 years ago1 comment1 person in discussion
Is it ok to say that EP problems are different from distributed computing ones and are thus well suited to large distributed platforms? I see it in the intro. --Javalenok (talk) 13:20, 24 April 2012 (UTC)Reply
Bitcoin
Latest comment: 13 years ago1 comment1 person in discussion
I'm a fan of bitcoin and studied maths but it took me some time to understand why:
"In Bitcoin mining, blocks with different nonces can be hashed separately."
is "embarrassingly parallel". In mining, a large set of data is hashed and then this small hash is hashed again like hash(hash + nonce). This can be delegated to several CPUs, GPUs, FPGAs (, ASICs?) or mining pool clients.
Actually the whole list is pretty hard to understand for non-experts of the respective fields.
What should be done? Should I explain a bit more about bitcoin mining with links?
--Giszmo (talk) 23:34, 1 January 2013 (UTC)Reply
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.