In computer jargon, a pipeline is a set of data processing elements connected in series, so that the output of one element is the input of the next one. The elements of a pipeline are often executed in parallel or in time-sliced fashion; in that case, some amount of buffer storage is often inserted between elements.

Computer-related pipelines include:

• Instruction pipelines, such as the classic RISC pipeline, which are used in processors to allow the parallel execution of two or more consecutive instructions from a nominally sequential stream; the processing elements are the logical circuits that implement the various stages of an instruction (address decoding and arithmetic, register fetching, cache lookup, etc.).
• Graphics pipelines, found in most graphics cards, which consist of multiple arithmetic units, or complete CPUs, that implement the various stages of common rendering operations (perspective projection, window clipping, color and light calculation, rendering, etc.).
• Software pipelines, consisting of multiple processes arranged so that the output stream of one process is automatically and promptly fed as the input stream of the next one. Unix pipelines are the classical implementation of this concept.

Concept and motivation

Pipelining is a natural concept in everyday life, e.g. when doing laundry. After the first load of laundry comes out of the washer and is placed in the dryer a second load can be put in the washer, without waiting for the drying to finish. If washing takes 30 minutes, and drying takes 60 minutes, a single load will take 90 minutes; but two loads can be done in 150 minutes. After one load of laundry goes through the system, a new one will finish every 60 minutes.

Costs and benefits

As the laundry example shows, pipelining doesn't decrease the time for a single datum to be processed; it only increase the throughput of the system when processing a stream of data.

A pipelined system typically requires more resources (circuit elements, processing units, computer memory, etc.) than one that executes one batch at a time, because its stages cannot reuse the resources of a previous stage. Moreover, pipelining may increase the time it takes for an instruction to finish.

Design considerations

One key aspect of pipeline design is balancing pipeline stages. Using the laundry example, we could have greater time savings if both the washer and dryer both took only 45 minutes. Although the system latency would still be 90 minutes, we would be able to output a new load of laundry every 45 minutes. If the wash only took 30 minutes and the dryer took 60, the washer would be idle for 30 minutes every hour (50% of the time).

Another design consideration is the provision of adequate buffering between the pipeline stages — especially when the processing times are irregular, or when data items may be created or destroyed along the pipeline.

See also

• Throughput
• Latency
• Parallelism
• Superpipelined