From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D3CEE138334 for ; Sun, 16 Dec 2018 11:34:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7B7F5E0B5D; Sun, 16 Dec 2018 11:34:21 +0000 (UTC) Received: from mail-pl1-f194.google.com (mail-pl1-f194.google.com [209.85.214.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 36B20E0AFA for ; Sun, 16 Dec 2018 11:34:21 +0000 (UTC) Received: by mail-pl1-f194.google.com with SMTP id 101so4799630pld.6 for ; Sun, 16 Dec 2018 03:34:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=yFnSSI7jKIeCh5JM+5hxIPqu6Zfa0FAMD6ldWmep/8I=; b=VrigxocfZpqVkW79nsvbhhBLcWD9vi3cnheF7QyCcXjtriaIXw+5Hrijs+emq1HZVk tIEcTLt3u1n8FR5/7saGgf0HqZm1DenEMqwZ2QmFi4p11JQzwJJcmGyIcmwo+4feEa2R gJg8xdr35juElk996ahtpjbDbPOwTxxwTcabcKXeamblwkGlT6ChgmkwcgfDjF/Zcpw1 XMdiYrBhEcoaO6uS1qMppoqcSNJNGfeMoX9ymu3X5uFaCllaHuo7mi1sXl0tYDenD2LO Ho7SGJSK3qECsu54RW2jtYZ5jOW34W9sZRxZ8OJ/foYApjTm6hvBY3ixZS9AZKD8gbvG T3KA== X-Gm-Message-State: AA+aEWY+5hA5Ex2c0CyEp3os04K30BowzCfbM+ZHssV9FlJxEW6myM5N 7lwfRNEXQamdh/Xcelv00xgef3D7/5sOteDeV95o3Prw X-Google-Smtp-Source: AFSGD/UQczIXHgZPF5RZRkTfnwnUXK1HU5t4kZpYsUR4wI2vHBRIOMkMHehCVJ13fFll6ryxKGt52ScVjUFNbw0lMZA= X-Received: by 2002:a17:902:b01:: with SMTP id 1mr9329098plq.331.1544960059012; Sun, 16 Dec 2018 03:34:19 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: In-Reply-To: From: Rich Freeman Date: Sun, 16 Dec 2018 06:34:07 -0500 Message-ID: Subject: Re: [gentoo-project] RFC: Dropping rsync as a tree distribution method To: gentoo-project Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 0d95dd3a-8795-4524-a303-db74e3cd25d9 X-Archives-Hash: d47cda5231c8ee07acbc0bf3b5fe8d3b On Sat, Dec 15, 2018 at 11:15 PM Alec Warner wrote: > > [1] Rich talked about some downsides earlier at https://lwn.net/Articles/759539/; but while these are challenges (some fixable) they are not necessarily blockers. The thread has already touched on a few of those comments. Despite only six months elapsing since I wrote that email, #1 no longer applies, and it sounds like #4 may not be as much of a concern. As you've already stated #3 can be easily addressed - setting up a git mirror is very easy. I think #2 is more of a fundamental design difference that probably will never go away. If your tree is a year old then git WILL take longer and transfer more data than rsync. My guess is that it will also cost more IO server-side than rsync, but it probably will be cheaper in CPU. However, I bet that 95% of our users sync weekly or daily and in that use case it is going to go a lot faster, and probably be less mirror load as well, and it will be a TON less IO load on the client side. I'm not sure how much IO cost there is to git garbage collection - that might offset this in the common shallow clone scenario. I'd suggest that those with concerns give it a shot using Zac's suggested settings and see how it goes. Really all you have to do is delete your local repo and adjust your sync settings and resync. I think the local disk use is going to be the biggest source of user objection and I'm interested in what people observe here. -- Rich