News for hackers. Stuff that matters.
Re:Pipe Viewer by londons_explore on Wednesday October 19, 2022 @11:11AM (#33263382)
It would be nice to indicate if the upstream or the downstream is the 'limiting' factor in speed.

Ie. within pv, is it the reading the input stream or the writing the output stream that is blocking most of the time?

Re:Pipe Viewer by ketralnis on Wednesday October 19, 2022 @12:18PM (#33264386)
It's open source, be the change you want to see in the world
Re:Pipe Viewer by kotlin2 on Wednesday October 19, 2022 @03:25PM (#33266761)
Having maintained an open source library, it’s actually really helpful to see features people want. Not everyone needs to contribute directly to the code base. User feedback is valuable, too.
Re:Pipe Viewer by ranger_danger on Wednesday October 19, 2022 @07:38PM (#33269173)
Unfortunately not everyone is a developer.
Re:Pipe Viewer by senjin on Wednesday October 19, 2022 @02:47PM (#33266290)
This would be a genius addition
Re:Pipe Viewer by bingaling on Wednesday October 19, 2022 @04:00PM (#33267254)
it's instantaneous, but the -T (transfer buffer % full display) is sometimes useful for that. (0% full -> source limited, 100% full -> sink limited)
Re:Pipe Viewer by Twirrim on Wednesday October 19, 2022 @04:52PM (#33267791)
Oh wow, I'd completely missed that -T flag. That's some useful data. Thanks for mentioning it!
Re:Pipe Viewer by tanelpoder on Wednesday October 19, 2022 @08:39PM (#33269580)
I have written a (free OSS) Linux tool called `psn` for this kind of stuff [1]. It samples each interesting thread's state from /proc/PID/task/TID/status,wchan,syscall etc and shows you a summary of which threads were blocked in which state, in which syscalls and where in the kernel were they stuck (wchan). It can be used with applications like pv, tar, dd, mysqld, httpd, etc.

[1] https://0x.tools/#linux-process-snapper