Talk:Consistency model

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing / CompSci / Hardware (Rated Start-class, Low-importance)
WikiProject icon 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.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 Low  This article has been rated as Low-importance on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Computer science (marked as Mid-importance).
Taskforce icon
This article is supported by Computer hardware task force (marked as Mid-importance).
 

Welch and Tanenbaum sources[edit]

I notice that the external link to lecture notes suggest that they are copyright Ian Welch 2004. However, the slides bear a striking resemblance to Andrew Tanenbaum's slides that accompany Chapter 6 of his Distributed Systems book[1]. I'm not sure of the policy regarding this. Any thoughts? Tim Watson 18:18, 24 January 2006 (UTC)

Programmer's rules[edit]

What are these "rules" that a programmer must follow to maintain consistency? —Preceding unsigned comment added by 128.138.64.20 (talk) 05:45, 27 February 2008 (UTC)

Confusion[edit]

The article says "To hold the contract, compilers may reorder some memory instructions". It is widely known that the reverse is true: the compiler may reorder instructions to optimize the code, but in some cases to ensure consistency this must be prevented (by usage of locking constructs or optimization barriers). I'm not sure if the author meant something else, or if this is plain confusion. --Blaisorblade (talk) 05:31, 26 December 2008 (UTC)

I was confused by that as well. I don't think consistency is an issue in those languages, because it is assumed that there is only one copy of data that gets stored in memory. If I understand the term "consistent" correctly, the issue applies only when there are multiple copies of the same data. BTW, if that's a correct statement, some version of it should appear in this article. Danielx (talk) 09:04, 18 October 2009 (UTC)

Begs the question[edit]

Instead of defining it, the first paragraph begs the question. Please add a definition of the concept to the first sentence. —Preceding unsigned comment added by 128.61.119.63 (talk) 19:49, 29 April 2011 (UTC)

What question are you talking about? ToddBradley (talk) 15:59, 31 January 2013 (UTC)

Non-sequitur[edit]

The one-sentence paragraph "Verifying sequential consistency is undecidable in general, even for finite-state cache-coherence protocols" really reads like a non-sequitur here. This section is an introduction and overview of consistency models, and here is suddenly a sentence containing one specific fact about "sequential consistency" without context. I'm not an expert in this field, but it seems like this fact (that verifying it is "undecidable in general") should be in the separate article about sequential consistency. ToddBradley (talk) 15:59, 31 January 2013 (UTC)

Data-centric vs. client-centric[edit]

Some academics (e.g., [1]) divide consistency models into data-centric, how what consistency rules are enforced when looking at the distributed system globally, and client-centric, how the consistency rules look from a single client's perspective. Would it make sense to have such a division in this article too? --Cristiklein (talk) 10:45, 7 January 2014 (UTC)

  1. ^ (PDF) http://www.cs.colostate.edu/~cs555/lectures/CS555-L18-Replication&Consistency-PartB.pdf.  Missing or empty |title= (help)