Differences between current version and predecessor to the previous major change of PipeLine.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Thursday, October 5, 2006 9:45:06 pm | by JohnMcPherson | |
| Older page: | version 1 | Last edited on Monday, April 19, 2004 1:31:59 am | by StuartYeates | Revert |
@@ -1,3 +1,12 @@
-A system in which several things are happening at once, but different parts of them are
+A system in which several things are happening at once.
-In a [CPU] the next instruction might be being decoded while the current one is being executed, that's a PipeLine. In a CommandLine the second command might start processing the output of the first command before the first command has terminated, that's also a PipeLine.
+There are several computer-related examples:
+
+#
In a [CPU] the next instruction might be being decoded while the current one is being executed, that's a PipeLine.
+#
In a CommandLine the second command might start processing the output of the first command before the first command has terminated, that's also a PipeLine.
+
+!CommandLine PipeLine hints
+There is a nifty little program called "pipe viewer" (debian/ubuntu - install "pv")
+that can give you a progress meter based on how much of a file has been processed.
+
+Eg, instead of ''grep pattern hugefile'', you can ''pv hugefile | grep pattern''. You can also insert it into the middle of a pipeline and give it options telling it the length of stdin, and if it can't work out the length it can give you statistics such as how fast the data is being processed. Neat
.
