It is and always was 100% a hallucination that piping to Out-Null was slower. How about =$null? friggin SLOWER! So, as the last three simple tests show, the Out-Null is actually FASTER in many cases when the pipeline is already in use. The horrible Out-null was 32339.3792 milliseconds, but wait - how much faster was casting to ? 34121.9251 ms?!? WTF? These are REAL #s on my system, casting to VOID was actually SLOWER. Proof, the last 3 tests in the list below. In other words, as soon as you pipe to anything, the whole rule of not using out-null goes into the trash. In fact, if you run the tests below you will quickly see that the same "faster" casting to and $void= that for years we all used thinking it was faster, are actually JUST AS SLOW and in fact VERY SLOW when you add ANY pipelining whatsoever. I realize this is an old thread, but for those taking accepted answer above as fact, I'm surprised it has not been corrected many of us have known for years it is actually the PIPELINE adding the delay and NOTHING to do with whether it is Out-Null or not. But I think it shows a clear reason to not use Out-Null. The numbers here varied a bit from test to test (I ran each about 5 times and picked the middle ground).
While > $null has an overhead of about 4%.
Here again Out-Null has about a 60% overhead. I just did some tests of the four options that I know about.
0 kommentar(er)
