Author: Irios
Subject: psping.exe -q doesnt really make it quiet
Posted: 23 December 2014 at 3:03pm
Wow, thanks. This is very interesting. I never knew about STDOUT and STDERR.
So my next question is, why are the pstools outputting stuff in this manner? Why is the output split up like this? Is there any practical use for it? I can only imagine the number of people struggling with the same type of problem like I had, but never figuring out how to solve it.
Another interesting thing I noticed after you told me this...
When STDERR is redirected to NUL, I get a lot different (better!) latency times.
It seems like when the copyright info and progress percent goes to the screen it affects the measurements (or the calculations) and creates jitter.
I tested with PingPlotter and ping (cmd) to compare results from PsPing because I was experiencing a lot of crazy jitter with the output from PsPing.
Note: I am pinging a server with low latency. Usually in the range of 2-3ms. And I would have very inaccurate PsPing results, sometimes up to 20ms higher than real ping
See graph here:
![]()
(red area is where STDERR is going to screen, the time period after this is where STDERR goes to NUL)
EDIT: This graph shows average latency of 5 pings in PsPing done once every 60 second. So the "real" numbers on the latency spikes are a lot higher than what you actually see in the graph.
PingPlotter from the same period of time
![]()
EDIT: This graph shows one ping per second
Edited by Irios - 17 hours 20 minutes ago at 3:09pm
Subject: psping.exe -q doesnt really make it quiet
Posted: 23 December 2014 at 3:03pm
Wow, thanks. This is very interesting. I never knew about STDOUT and STDERR.
So my next question is, why are the pstools outputting stuff in this manner? Why is the output split up like this? Is there any practical use for it? I can only imagine the number of people struggling with the same type of problem like I had, but never figuring out how to solve it.
Another interesting thing I noticed after you told me this...
When STDERR is redirected to NUL, I get a lot different (better!) latency times.
It seems like when the copyright info and progress percent goes to the screen it affects the measurements (or the calculations) and creates jitter.
I tested with PingPlotter and ping (cmd) to compare results from PsPing because I was experiencing a lot of crazy jitter with the output from PsPing.
Note: I am pinging a server with low latency. Usually in the range of 2-3ms. And I would have very inaccurate PsPing results, sometimes up to 20ms higher than real ping
See graph here:
(red area is where STDERR is going to screen, the time period after this is where STDERR goes to NUL)
EDIT: This graph shows average latency of 5 pings in PsPing done once every 60 second. So the "real" numbers on the latency spikes are a lot higher than what you actually see in the graph.
PingPlotter from the same period of time
EDIT: This graph shows one ping per second
Edited by Irios - 17 hours 20 minutes ago at 3:09pm