> As the initial competition requirements are likely vague, I'd imagine it's unclear if this is still good wrt the rules. You can scroll upward to the original

> As the initial competition requirements are likely vague, I'd imagine it's unclear if this is still good wrt the rules. You can scroll upward to the original question to see the initial requirements, and check the edit history to verify that they haven't changed since the start of the challenge: > Write your fizz buzz program. Run it. Pipe the output through <your_program> | pv > /dev/null. The higher the throughput, the better you did. > The program output must be exactly valid fizzbuzz. No playing tricks such as writing null bytes in between the valid output - null bytes that don't show up in the console but do count towards pv throughput. And vmsplice(2) indeed produces a stream of bytes in the standard output pipe that pv(1) can splice into /dev/null, or cat(1) can copy into the terminal. This submission was not the only one that uses vmsplice(2); others have found that it's far from a magic bullet. Once you pass the I/O hurdle, much work remains in generating the pages of output as quickly as possible.