3 ms·

Think they were generating load? Going through the urandom device not bad as it has to do a bit of work to get that rand number? Just for throughput though ze

• yakubin 4y ago
  I don't understand. If you're testing how fast pipes are, then I'd expect you to measure throughput or latency. Why would you measure how fast something unrelated to pipes is? If you want to measure this other thing on the other hand, why would you bother with pipes, which add noise to the measurement? UPDATE: If you mean that you want to test how fast pipes are when there is other load in the system, then I'd suggest just running a lot of stuff in the background. But I wouldn't put the process dedicated for doing something else into the pipeline you're measuring. As a matter of fact, the numbers I gave were taken with plenty of heavy processes running in the background, such as Firefox, Thunderbird, a VM with another instance of Firefox, OpenVPN, etc. etc. :)
  • khorne 4y ago
    Because they mentioned generating load, not testing pipe performance.
    • yakubin 4y ago
      Oh, wait. You mean that this "cat </dev/urandom >/dev/null" was meant to be running in the background and not be the pipeline which is tested? Ok, my bad for not getting the point.
• gtirloni 4y ago
  "Generating load" for measuring pipe performance means generating bytes. Any bytes. urandom is terrible for that.