hseq
unpolished faster implementation of seq (by tverniquet)
pipes-speed-test | hseq | |
---|---|---|
1 | 1 | |
149 | 1 | |
- | - | |
1.8 | 10.0 | |
almost 2 years ago | almost 8 years ago | |
Assembly | C | |
GNU General Public License v3.0 or later | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pipes-speed-test
Posts with mentions or reviews of pipes-speed-test.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-02.
-
How fast are Linux pipes anyway?
There's an outer while(true){} loop - the write side just writes continuously.
More generally though, sidenote 5 says that the code in the article itself is incomplete and the real test code is available in the github repo: https://github.com/bitonic/pipes-speed-test
hseq
Posts with mentions or reviews of hseq.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-02.
-
How fast are Linux pipes anyway?
I once had to change my mental model for how fast some of these things were. I was using `seq` as an input for something else, and my thinking was along the lines that it is a small generator program running hot in the cpu and would be super quick. Specifically because it would only be writing things out to memory for the next program to consume, not reading anything in.
But that was way off and `seq` turned out to be ridiculously slow. I dug down a little and made a faster version of `seq`, that kind of got me what I wanted. But then noticed at the end that the point was moot anyway, because just piping it to the next program over the command line was going to be the slow point, so it didn't matter anyway.
https://github.com/tverniquet/hseq
What are some alternatives?
When comparing pipes-speed-test and hseq you can also consider the following projects:
endoflife.date - Informative site with EoL dates of everything
pv - Pipe Viewer Mirror - 1.6
public-iperf3-servers - A list of public iPerf3 servers...