Producer/Consumer - Revision history

Q at 14:56, 20 July 2021

2021-07-20T14:56:52Z

← Older revision		Revision as of 14:56, 20 July 2021
Line 1:		Line 1:
	Use the '''Producer/Consumer''' ~~design pattern for~~ data sharing between multiple loops running at different rates. The Producer/Consumer pattern’s parallel loops break down into two categories; those that produce data, and those that consume the data produced. Data queues communicate data between loops in the Producer/Consumer design pattern. These queues offer the advantage of data buffering between producer and consumer loops.		Use the '''Producer/Consumer''' [[Design Patterns\|design pattern]] for data sharing between multiple loops running at different rates. The Producer/Consumer pattern’s parallel loops break down into two categories; those that produce data, and those that consume the data produced. Data queues communicate data between loops in the Producer/Consumer design pattern. These queues offer the advantage of data buffering between producer and consumer loops.
	[[File:Producer-Consumer Design Pattern.png\|center\|frameless\|572x572px\|Producer/Consumer Design Pattern]]		[[File:Producer-Consumer Design Pattern.png\|center\|frameless\|572x572px\|Producer/Consumer Design Pattern]]

Q: Category reorg

2020-06-03T16:33:19Z

Category reorg

← Older revision		Revision as of 16:33, 3 June 2020
Line 10:		Line 10:
	<references />		<references />

	[[Category:Design ~~patterns~~]]		[[Category:Basic Design Patterns]]

Q: Added content from the FANDOM site.

2018-11-11T03:30:12Z

Added content from the FANDOM site.

← Older revision		Revision as of 03:30, 11 November 2018
Line 1:		Line 1:
	~~{{stub}}~~		Use the '''Producer/Consumer''' design pattern for data sharing between multiple loops running at different rates. The Producer/Consumer pattern’s parallel loops break down into two categories; those that produce data, and those that consume the data produced. Data queues communicate data between loops in the Producer/Consumer design pattern. These queues offer the advantage of data buffering between producer and consumer loops.
			[[File:Producer-Consumer Design Pattern.png\|center\|frameless\|572x572px\|Producer/Consumer Design Pattern]]

	[[~~category~~:~~design~~ patterns]]		The Producer/Consumer pattern gives you the ability to easily handle multiple processes at the same time while iterating at individual rates. What makes this pattern unique is its added benefit of buffered communication between application processes. When there are multiple processes running at different speeds, buffered communication between processes is extremely effective. For example, an application has two processes. The first process performs data acquisition and the second process takes that data and places it on a network. The first process operates at three times the speed as the second process. If the Producer/Consumer design pattern is used to implement this application, the data acquisition process will act as the producer and the network process the consumer. With a large enough communication queue (buffer), the network process will have access to a large amount of the data that the data acquisition loop acquires. This ability to buffer data will minimize data loss.<ref>"Application Design Patterns: Producer/Consumer" by National Instruments (http://www.ni.com/white-paper/3023/en/)</ref>

			== Use Cases ==
			Add yours here

			== References ==
			<references />

			[[Category:Design patterns]]

Q: Q moved page Producer consumer to Producer/Consumer: Fixing Title

2018-11-11T03:27:49Z

Q moved page Producer consumer to Producer/Consumer: Fixing Title

← Older revision	Revision as of 03:27, 11 November 2018
(No difference)

Michael_Aivaliotis at 10:53, 8 October 2007

2007-10-08T10:53:08Z

← Older revision		Revision as of 10:53, 8 October 2007
Line 1:		Line 1:
	{{stub}}		{{stub}}

	[[~~Category~~:~~Design Patterns~~]]		[[category:design patterns]]

Michael_Aivaliotis: Producer/consumer moved to Producer consumer: forward slash not allowed in page name, denotes parent child page relationship.

2007-10-08T10:52:43Z

Producer/consumer moved to Producer consumer: forward slash not allowed in page name, denotes parent child page relationship.

← Older revision	Revision as of 10:52, 8 October 2007
(No difference)

Michael_Aivaliotis at 08:38, 1 October 2007

2007-10-01T08:38:50Z

← Older revision		Revision as of 08:38, 1 October 2007
Line 1:		Line 1:
	~~This is a~~ stub ~~article for the producer/consumer architecture.~~		{{stub}}

	[[Category:Design Patterns]]		[[Category:Design Patterns]]
	~~[[Category:Stubs]]~~

Eaolson: add stub cat

2007-05-12T22:56:53Z

add stub cat

← Older revision		Revision as of 22:56, 12 May 2007
Line 2:		Line 2:

	[[Category:Design Patterns]]		[[Category:Design Patterns]]
			[[Category:Stubs]]

Eaolson: create stub

2007-05-09T17:57:53Z

create stub

New page

This is a stub article for the producer/consumer architecture.

[[Category:Design Patterns]]