Linked by David Adams on Fri 5th Aug 2011 16:08 UTC
Thread beginning with comment 484283
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2011-08-06
Like looking in some database thing and grep out of it. It's faster with bash, because it uses small pipes instead of buffering the whole stuff, even if the text is already there.It will presented at the end.
Ahem! PowerShell objects are *streamed* as well; they are pushed through the pipeline one-by-one. Because it is all in-process what is pushed through the pipeline is actually only an in-memory pointer. That is arguably both *faster* and more memory-efficient than constantly serializing to/from strings.
I don't know where you have gotten the idea that PowerShell would buffer everything until the end?
Once an object has been passed on through the pipeline it is eligible for garbage collection. Large datasets will not need to be allocated all at once.
Powershell in it's best for is a small subset of what scripting can do under unix type of operating systems.
PowerShell is much more capable than unix/linux *sh style shell scripting, more consistent, more robust and more secure.