On Wed, Jun 20, 2018 at 06:01:21PM +0200, Maximilian Pichler wrote: > On Wed, Jun 20, 2018 at 5:50 PM, Solene Rapenne <sol...@perso.pw> wrote: > > it's slow because it flushes the output every byte, what would you > > expect? Maybe you should do in a different manner. > > I know, my question is what such a different manner might look like. :)
On my Linux box: cat HUGE | /usr/bin/time dd bs=1 count=1234944 | wc -c 1234944+0 records in 1234944+0 records out 1234944 bytes (1.2 MB) copied, 4.33782 s, 285 kB/s 0.33user 4.00system 0:04.34elapsed 99%CPU (0avgtext+0avgdata 772maxresident)k 0inputs+0outputs (0major+249minor)pagefaults 0swaps 1234944 cat HUGE | /usr/bin/time dd bs=1024 count=1206 | wc -c 1206+0 records in 1206+0 records out 1234944 bytes (1.2 MB) copied, 0.00895034 s, 138 MB/s 0.00user 0.00system 0:00.01elapsed 66%CPU (0avgtext+0avgdata 768maxresident)k 0inputs+0outputs (0major+248minor)pagefaults 0swaps 1234944 -- Regards, Tomasz Rola -- ** A C programmer asked whether computer had Buddha's nature. ** ** As the answer, master did "rm -rif" on the programmer's home ** ** directory. And then the C programmer became enlightened... ** ** ** ** Tomasz Rola mailto:tomasz_r...@bigfoot.com **
