2 ms·
I presume somebody had a need, and scratched the itch. With modern systems we can have 8 channel RAM and 128 PCIe lanes to feed a system stuffed with NVMe driv
by dale_glass 3y ago
I presume somebody had a need, and scratched the itch.
With modern systems we can have 8 channel RAM and 128 PCIe lanes to feed a system stuffed with NVMe drives. The amount of throughput that can be obtained is nuts, and at that point all sorts of weird things can become an unexpected bottleneck.
This applies even in consumer systems. Suddenly your game loads far slower on a NVMe than it could because it never occurred to the programmer that instead of the disk, the JPEG decoder can become a bottleneck when you can read compressed data at 7 GB/s.
- eichin 3y agoa decade or so ago, I ran into a problem where "yes" was already too fast, feeding it to apt-get install or something (in a context where we knew what the prompts were doing and if anything unusual happened we'd fail other checks immediately) and it had some clever input buffering going on... that wasn't clever enough and locked up on getting a megabyte of yes'es on the first read() call.
- shrubble 3y agoCheck out 'stdbuf' perhaps?