From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id CDACB138A1F for ; Sun, 26 Jan 2014 17:43:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DF014E0C67; Sun, 26 Jan 2014 17:43:00 +0000 (UTC) Received: from mail-we0-f170.google.com (mail-we0-f170.google.com [74.125.82.170]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B0B66E0C07 for ; Sun, 26 Jan 2014 17:42:59 +0000 (UTC) Received: by mail-we0-f170.google.com with SMTP id u57so4488313wes.1 for ; Sun, 26 Jan 2014 09:42:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=GH+vWoho2kvZ3sPHN9MTP1Emdea8+4uJEGfyDqKbOvM=; b=gS/jXWVZLZfaPA6lxhXvM1sjBUZg9EsayXAokjT0ya+2df1OfydIsUq5WPxoEJxP70 3h+fw6St6rnThiznnvEh5ClX6DTcWjETsIiHRy8hGBBBlSb5LPj5yUanY0hJduyAUqiK AfQTeHXY1TTB8hZWYd0LQd3Sb5eBuetpIoEsqSOvnHVkdM5gshiWveTxKCoPrTl6oYo5 DxechSHo++m5S4EonSmMHw1T+k9ynWXGtI0FPU1dn4RECjzmudio43TTvX7BauKmNhii LAZGIhO1feof7DqdOuJGcuyLu/7BByg8DvycTyxiux8olsmIntC7cOxPtwblw9iypKpc 4h9A== X-Received: by 10.180.90.37 with SMTP id bt5mr9443741wib.43.1390758178346; Sun, 26 Jan 2014 09:42:58 -0800 (PST) Received: from [172.20.0.40] (196-210-244-37.dynamic.isadsl.co.za. [196.210.244.37]) by mx.google.com with ESMTPSA id ff9sm22987348wib.11.2014.01.26.09.42.56 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 Jan 2014 09:42:57 -0800 (PST) Message-ID: <52E54920.5010207@gmail.com> Date: Sun, 26 Jan 2014 19:42:56 +0200 From: Alan McKinnon User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Portage performance dropped considerably References: <20140126162426.7a6d1f30@falcon.eroen.eu> In-Reply-To: <20140126162426.7a6d1f30@falcon.eroen.eu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 2b9ef376-3d9c-443d-bbd7-122e4d9f1017 X-Archives-Hash: 83c64a44bf8baf0f65984bb6c30d47c9 On 26/01/2014 17:24, eroen wrote: > On Sun, 26 Jan 2014 16:35:43 +0200, Nikos Chantziaras > wrote: >> Anyone else noticed this yet? Some portage update seems to have made >> "emerge -uDN @world" perform about 10 times slower than before. It >> used to take seconds, now it takes about 4 minutes only to tell me >> that there's nothing to update. And it does that every time, even >> directly in succession and with the caches warm. >> >> Is it just me? > > You don't say when your baseline was, but the complexity of resolving > the package tree has increased quite a bit over the last year due to > new features like automatic rebuilds of consumers after library updates. > > Another somewhat common cause of sudden slowdowns is how portage > resolves conflicts (like packageA requiring an old version of libraryB), > which is rather time-consuming. You can try adding --backtrack=0 to the > emerge command to make it stop and print an error message when > encountering a conflict rather than look for a solution. Then you can > 'help' out by manually resolving any conflicts by adding package > versions to /etc/portage/package.mask . Preferably try this *after* > running an update, so your system is up-to-date against your local > version of the gentoo tree, otherwise "normal" simple-to-resolve > conflicts might cause confusion. ;-) > I've been noticing these slowdowns for a few months now too. I'm somewhat conflicted in my head about them, as unresolved blockers is now something that happens very rarely. How often did we do this in the past: emerge -avuND world stare at output trying to figure out wtf? emerge -C emerge -avuND world emerge problem package back if world update didn't already do it That used to happen A LOT, and it took much longer than 4 minutes. Nowadays it happens seldom but the resolution does take 4 minutes. So I dunno, it's annoying to have to wait, but it also prevents a lot of wasted time by doing what software can do so well - detecting dependency issues. -- Alan McKinnon alan.mckinnon@gmail.com