Cache Guide, Meaning , Facts, Information and Description

This article is about the computer term. For towns with this name, see Cache, Utah or Cache, Oklahoma and for general sense Cache in general.

The reason caches work at all is that many access patterns in typical computer applications have locality of reference. There are several sorts of locality, but we mainly mean that often the same data is accessed frequently or with accesses that are close together in time, or that data near to each other are accessed close together in time.

Policies

In computing a No-write allocation is a cache policy where only processor reads are cached, thus avoiding the need for write-back or write-through.

Types

Small memories on or close to the CPU chip can be made faster than the much larger main memory. Most CPUs since the 1980s have used one or more caches, and modern general-purpose CPUs inside personal computers may have a dozen, each specialized to a different part of the problem of executing programs.

Disk caches

Hard disks have historically often been packaged with embedded computers used for control and interface protocols. Since the late 1980s, nearly all disks sold have these embedded computers and either an ATA, SCSI, or Fibre Channel interface. The embedded computer usually has some small amount of memory which it uses to cache the bits going to and coming from the disk platter.

The disk cache is physically distinct from and is used differently than the page cache typically kept by the operating system in the computer's main memory. The disk cache is controlled by the embedded computer in the disk drive, where the page cache is controlled by the computer to which that disk is attached. The disk cache is usually quite small, 2 to 8 MB, where the page cache is generally all unused physical memory, which in a 2004 PC may be between 20 and 2000 MB. And while data in the page cache is reused multiple times, the data in the disk cache is typically never reused. In this sense, the phrase disk cache is a misnomer, and it might more appropriately be called the disk buffer. But that is not the phrase typically used.

The disk cache has multiple uses:

• Readahead / readbehind: When executing a read from the disk, the disk arm will move the read/write head to (or near) the correct track, and after some settling time the read head will begin to pick up bits. Usually, the first sectors to be read are not the ones that have been requested by the operating system. The disk's embedded computer will typically save these unrequested sectors in the disk cache, in case the operating system requests them later.

• Speed matching: The speed of the disk's I/O interface to the computer almost never matches the speed at which the bits are transferred to and from the platter. The disk cache is used as a buffer so that both the I/O interface and the disk read/write head can operate at full speed.

• Write acceleration: The disk's embedded computer may signal the main computer that a disk write is complete immediately after receiving the write data, before the data is actually written to the platter. This early signal allows the main computer to continue working, but is somewhat dangerous because, if power is lost before the data is permanently fixed in the magnetic media, the filesystem may be left in an inconsistent state. Write acceleration is controversial, and for this reason can usually be turned off. On some disks, this vulnerable period between signalling the write complete and fixing the data can be arbitrarily long, as the write can be deferred indefinitely by newly arriving requests. Write acceleration is generally never used on database servers or other machines where the integrity of the data on the disks is very important.

• Command queueing: Newer SATA and most SCSI disks can accept multiple commands while any one command is in operation. These commands are stored in the disk's embedded computer until they are completed. Should a read reference the data at the destination of a queued write, the write's data will be returned. Command queueing is different than write acceleration in that the main computer's operating system is notified when data is actually written onto the magnetic media. The O/S can use this information to keep the filesystem consistent through rescheduled writes.

Caching for reading access only is common when operating over networks, because the coherency protocol may become exceedingly complicated if communication is not reliable. For instance, web page caches and client-side network file system caches (like those in NFS or SMB) are typically read-only specifically to keep the network protocol simple and reliable.

A cache of recently visited web pages can be managed by your Web browser. Some browsers are configured to use an external proxy web cache, a server program through which all web requests are routed so that it can cache frequently accessed pages for everyone in an organization. Many ISPs use proxy caches to save bandwidth on frequently-accessed web pages.

The search engine Google keeps a cached copy of each page it examines on the web. These copies are used by the Google indexing software, but they are also made available to Google users, in case the original page is unavailable. If you click on the "Cached" link in a Google search result, you will see the web page as it looked when Google indexed it.

Ccache is a program that caches the output of the compilation to speed up the second-time compilation.

See also

• Cache algorithms
• Change management
• CPU cache

• "An Asynchronous Avoidance-Based Cache Consistency Algorithm for Client Caching DBMSs" by M. Tamer Özsu, Kaladhar Voruganti, Ronald C. Unrau
• "A Unified Algorithm for Cache Replacement and Consistency in Web Proxy Servers" by Junho Shim, Peter Scheuermann, Radek Vingralek

This is an Article on Cache. Page Contains Information, Facts Details or Explanation Guide About Cache

	Web www.E-paranoids.com