Gentoo Archives: gentoo-portage-dev

From: James Cloos <cloos@×××××××.com>
To: Zac Medico <zmedico@g.o>
Cc: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] portage 9999 at commit 2d5e38b495776e5bb2266848a3365667f3ca7233 **SLOW**
Date: Wed, 01 May 2013 20:57:54
Message-Id: m3vc72mn9z.fsf@carbon.jhcloos.org
In Reply to: Re: [gentoo-portage-dev] portage 9999 at commit 2d5e38b495776e5bb2266848a3365667f3ca7233 **SLOW** by Zac Medico
1 >>>>> "ZM" == Zac Medico <zmedico@g.o> writes:
2
3 ZM> On 04/30/2013 11:19 PM, James Cloos wrote:
4 >> My typical emerge -upvDN world went up from 10s of minutes to several
5 >> hours sometime between portage 37f33e9 and 2d5e38b.
6
7 ZM> I don't see any regressions on my end. Please feel free to bisect those
8 ZM> commits and isolate it to a particular one. :)
9
10 Before trying that, I tried reverting 62dbcaa4d873784f1 and that worked.
11 emerge -upvDN world only took:
12
13 User time (seconds): 682.19
14 System time (seconds): 432.78
15 Percent of CPU this job got: 91%
16 Elapsed (wall clock) time (h:mm:ss or m:ss): 20:17.37
17 Maximum resident set size (kbytes): 4628592
18 File system inputs: 260072
19 File system outputs: 907632
20
21 Note how it hit >4 GB RSS, though.
22
23 -JimC
24 --
25 James Cloos <cloos@×××××××.com> OpenPGP: 1024D/ED7DAEA6

Replies