From owner-freebsd-bugs@freebsd.org Wed Nov 29 20:47:10 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2F46DBB6FE for ; Wed, 29 Nov 2017 20:47:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 793E863FE8 for ; Wed, 29 Nov 2017 20:47:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vATKl9NJ089050 for ; Wed, 29 Nov 2017 20:47:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 223955] cpio needs a --block-size= option Date: Wed, 29 Nov 2017 20:47:09 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 9.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: rfg-freebsd@tristatelogic.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2017 20:47:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223955 Ronald F. Guilmette changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rfg-freebsd@tristatelogic.c | |om --- Comment #4 from Ronald F. Guilmette --- Oy vey! I think that I may perhaps want to withdraw this PR entirely, now = that I have some additional (and troubling) data. After I filed this PR, just for laughs, I tried using that --block-size cpio option on my Ubuntu system and then tried again to time a multi-gigabyte fi= le copy (cpio -p) which I had already times using other methods (e.g. "cp" and "cpio -without any --block-size=3D option). I did my test with --block-siz= e=3D1M. To my amazement and horror, adding the --block-size=3D1M option didn't real= ly make any huge difference. The bloody file copying was -still- running at l= east 5x slower than copying of a similar sized file using good old "cp". Moral of the story: I guess I'm the only one on the planet who is still ev= en trying to use good old cpio. it appears that all of the work and tuning and optimizations have gone into cp and/or rsync instead... both of which are f= ast snot... while leaving poor old cpio to wallow in the backwaters of virtual abandonment. Sigh. I find this rather a pity, because, given that cpio is MUCH simpler = than rsync, in theory it -should- be able to do file copies at least as fast, or perhaps even a bit faster. (It doesn't have the added burden of all the network awareness and all that fancy schmancy differential file comparison stuff to deal with, unlike rsync.) But it seems that I'm the only one in the universe who has even noticed, in= all the years of this century so far, that poor old cpio just hasn't been keepi= ng up. Thus, it is silly of me to try to swim against the tide. I'll just us= e cp and rsync from now on and be done with it. --=20 You are receiving this mail because: You are the assignee for the bug.=