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 0DF9C138247 for ; Mon, 13 Jan 2014 09:32:45 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2E7E6E0A99; Mon, 13 Jan 2014 09:32:39 +0000 (UTC) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 294F0E09EE for ; Mon, 13 Jan 2014 09:32:38 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id cc10so753414wib.11 for ; Mon, 13 Jan 2014 01:32:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:content-type:content-transfer-encoding; bh=fTtIT8lEsk8v+jbvmX2QTQM3PM8YxPE0B1GdWdIm36E=; b=DMGGG+zqzUtdOq6zk/guTxhaKQRkxbkXNoUZ/+NY4deT5BVZ27yncKBbC02uvCkzZA 38diHm3jqyM9W3m7cgvGQx8M+z8E3VAMiRuybagF0qj7NtWOBGaebCc2tllc+3o2wDfI jdoWY4UelJpNzjjczx9DwNqks+SOZLOrn/ThE09onV7Wau++ewkuAix9/qs6D7EGF3IY N7zkLrp+CHBFj/n+8Jf9d+tj3+Br33K/TpJyS2RsU+l3LhEVPPO3oGFqay47ULlar8rG dAw1QYRawqjabw2mikrk3mBTCNJcLyE2OxZDCAhjMwDIWs5uApPqnwX1vWkd4x+QCZ/3 Wl0A== X-Gm-Message-State: ALoCoQk88Hr5+nT2cfO1MMv5PvuoIgDHE1YNHWjfOxtYM2Ow25vYtCqAn2cYhu4mHAMNe66dCK1I X-Received: by 10.180.75.115 with SMTP id b19mr14343325wiw.19.1389605556786; Mon, 13 Jan 2014 01:32:36 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Sender: lxnay@sabayonlinux.org Received: by 10.194.83.193 with HTTP; Mon, 13 Jan 2014 01:31:56 -0800 (PST) In-Reply-To: <52D3AEB9.7080500@pathscale.com> References: <1388986435.17870.49.camel@big_daddy.dol-sen.ca> <1389582464.7103.185.camel@big_daddy.dol-sen.ca> <20140113083917.5427344.53422.41690@pathscale.com> <52D3A71F.9040602@plaimi.net> <52D3AEB9.7080500@pathscale.com> From: Fabio Erculiani Date: Mon, 13 Jan 2014 10:31:56 +0100 X-Google-Sender-Auth: LGBRmpDNGSWVKjzSPFX4ycj9Sfg Message-ID: Subject: Re: [gentoo-dev] [OT] pkgcore bikeshed (was Portage team) To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 40844eb8-87d3-49d1-80c9-4cb5a9bcbb85 X-Archives-Hash: c1431af470522e7d08e9963e37e75468 On Mon, Jan 13, 2014 at 10:15 AM, "C. Bergstr=C3=B6m" wrote: > On 01/13/14 03:43 PM, Alexander Berntsen wrote: > Where I work uses pkgcore[1], but not the areas which are generally > beneficial to the whole community. (We use it as part of a web applicatio= n > to handle testsuites which have build dependencies.) We can blah blah abo= ut > performance of resolving package dependencies all day long, > [...] Not sure about what you mean with "blah blah". But given the amount of both disk caches (metadata, vdb cache) and memory caches (the in-memory aux_db cache that portage loads using pickle (it's a dict) takes like 70-100Mb of RAM on an average desktop system), Portage can still take *minutes* to calculate the merge queue of a pkg with all its deps satisfied. Ironically, launching the same emerge command twice, will take more or less the same time. Yeah, this is probably bad design... --=20 Fabio Erculiani