Talk:Concurrent computing

message: See Talk:Concurrent programming language for earlier discussions on concurrent programming languages, as well as dicussion on the merge into Concurrent computing. --Allan McInnes 07:03, 27 January 2006 (UTC)
thread_title:  Merged content from [[Concurrent programming language]] 

message: The concurrent computing article currently claims
:"However, since both processes perform their withdrawals, the total amount withdrawn will end up being more than the original balance. These sorts of problems with shared resources require the use of concurrency control, or non-blocking algorithms."
Currently, the concurrency control article seems to be talking *only* about databases.
What about all the algorithms listed in :Category:Concurrency control that involve blocking, but do not involve databases? Algorithms such as serializing tokens and mutual exclusion and monitor (synchronization)?
Aren't they also perfectly valid ways of dealing with this sort of problem?
We need to either
* Change this "concurrent computing" article to add another category of solutions, "These sorts of problems with shared resources require the use of concurrency control, ((new category here that includes monitors, etc.)), or non-blocking algorithms.". Or
* Change the concurrency control article to discuss all blocking algorithms (whether or not they require a database).
* change this "concurrent computing" article to *remove* a category of solutions, "These sorts of problems with shared resources require the use of concurrency control". And change the "concurrency control" article to discuss all the algorithms in :Category:Concurrency control, blocking and non-blocking.
What is a good name for this "new category" (things like monitors, mutexes, serializing tokens, etc)?
Or is there a better 4th option?
--70.189.73.224 15:08, 23 September 2006 (UTC)
thread_title:  what is concurrency control 

message: Atleast accordigng to CTM Book the three variants are 
* Shared memory concurrency
* Message Passing concurrency
* Dataflow concurrency
(i.e Dataflow is an independent branch)
Blufox (talk) 09:32, 1 October 2008 (UTC)
replies: text: Dataflow variables are a kind of future. The listing of shared memory and message-passing in the article is referring to forms of explicit communication between threads (as opposed to the presumably "implicit" communication inherent in a future). The implied dichotomy between futures and other methods of communication is perhaps not correct, and it's certainly not well explained in the article. If you'd like to take a stab at rewriting it, I'd be interested to see what you come up with. --Allan McInnes (talk) 23:24, 1 October 2008 (UTC)
thread_title:  Types of concurrency 

message: Can someone clean up the definition so someone can actually understand the difference between parallel and concurrent computing?
Parallel computing is the execution of the exact same algorithm at the same time.
Concurrent computing is the excetuion of multiple, but not necessarilly the same, software at the same time.
That's the only difference.  Parallel computing IS concurrent computing.  But concurrent computing is not always parallel computing.  Although unlikely, they don't need to interact either.—The preceding unsigned comment was added by 142.167.85.107 (talk) 07:42, 16 February 2007 (UTC)
thread_title:  Clearer definition 

message: Should this page be merged with Concurrency (computer science)? --FishSpeaker (talk) 03:15, 14 November 2008 (UTC)
replies: text: No, I don't think so. The Concurrency (computer science) article deals (or should deal) with defining the term "concurrency" as it's used in computer science, and discussing both its theoretical (some of which have little to do with concurrent computing) and practical aspects (in overview). The concurrent computing article should cover the practical aspects and applications of concurrency in programs. --Allan McInnes (talk) 01:43, 13 May 2009 (UTC)

text: No. They are different areas and involve different concerns. Concurrent computing involves writing programs that contain independent parts that may (but don't have to be) executed in parallel. For example, sometimes programs are made concurrent just to make them appear more responsive by running time-consuming but non-time-critical tasks "in the background", with no intention of running them on parallel processors. Parallel computing deals with the specific problems of writing programs intended to be run on multiple processors, typically to provide reductions in computation time. In that sense it's a subset of concurrent computing, but typically addresses other concerns in addition to concurrency. --Allan McInnes (talk) 01:43, 13 May 2009 (UTC)
thread_title:  Merge with [[Concurrency (computer science)]]? 

message: After describing shared memory and message passing styles, the article states "Typically (although not always), the ... overhead ... is lower in a message passing system".  ?!?  Shared memory systems are generally much faster than message-passing systems because the former can bypass data copy, serialization, etc.  Was this a typo?  If it was intentional, some justification should be given.
129.55.200.20 (talk) 19:01, 31 July 2013 (UTC)
thread_title:  Overhead question 

message: I removed the software pipeline example, because I'm not convinced it's an example of concurrency. The present article is doing its best to distinguish concurrency from parallelism (even though Pike, cited for the confusion between the two, actually connects them), and citing an obviously sequential algorithm (lex, parse, translate, assemble, link) isn't helping that cause. QVVERTYVS (hm?) 21:24, 9 January 2015 (UTC)
thread_title:  Removed the software pipeline example 

message: "Process Communication Model" can also refer to Taibi Kahler's Process Communication Model, a model of human communication that was used at NASA during the selection of shuttle astronauts and is now available for HR training. I'm currently researching Kahler and intend expanding his entry and adding one for his PCM. 
Any objections to a disambiguation page for "Process Communication Model"? If that term is searched it currently links directly to Concurrent Computing.
Aeon-lakes (talk) 02:48, 9 April 2015 (UTC)
thread_title:  PCM Disambiguation 

message: Hello fellow Wikipedians,
I have just modified 2 external links on Concurrent computing. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20100306171307/http://codespeak.net/py/0.9.2/greenlet.html to http://codespeak.net/py/0.9.2/greenlet.html
*Added archive https://web.archive.org/web/20060128114620/http://vl.fmnet.info/concurrent/ to http://vl.fmnet.info/concurrent/
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 00:30, 12 August 2017 (UTC)
thread_title:  External links modified 

message: Would it be appropriate for Bulk_synchronous_parallel to be added to the Models section?
46.208.236.121 (talk) 04:33, 24 May 2018 (UTC)
thread_title:  Should BSP be added to the Model section? 

message: I will remove the link if no one objects. Digital27 (talk) 14:17, 14 November 2023 (UTC)
thread_title:  What does sheaf have to do with concurrent programming?