Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a2223c22bd99a68e

Jump to content

Talk:3Cs model

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 7 years ago by 84.1.222.175 in topic C.C.C in agile/scrum

Untitled

[edit]

There is also a 3 C model of cache consistency in computer architecture.

I've been trying to find information on it, so I'm not qualified to build the page or disambiguate it from this one.

Find a reference to it, for instance, in the Communications of the ACM, April 2009, Samuel Williams et al "Roofline: An insightful visual performance model for Multicore Architectures", p 65, and also a number of Google hits on "3c cache model".

I also found a textbook with a brief description: David A Patterson and John L Hennessy, "Computer Organization and Design", 2nd Ed, Morgan Kaufmann Publishers, Inc, San Francisco, 1988.

Okay, so I made the stub.

kogorman (talk) 16:32, 15 May 2009 (UTC)Reply

fixed cost ratio

[edit]

The term fixed cost ratio seems to be defined in different ways throughout the Internet. Does this article mean fixed costs to variable costs ratio instead? — Preceding unsigned comment added by 121.7.202.253 (talk) 11:22, 17 June 2012 (UTC)Reply

C.C.C in agile/scrum

[edit]

I have come across the 3 C's in an agile training, where they denote preferred characteristics of a user story: Card, Conversation, Confirmation. A user story shall fit a an index card, shall trigger conversation and shall contain criteria of acceptance or confirmation.  Preceding unsigned comment added by 84.1.222.175 (talk) 23:43, 23 January 2019 (UTC)Reply