On Thursday, 3 May 2018 17:57:20 BST Neil Bothwick wrote: > On 3 May 2018 16:41:55 BST, Grant Edwards <grant.b.edwa...@gmail.com> wrote: > >On 2018-05-03, Mick <michaelkintz...@gmail.com> wrote: > >> OK, I know my laptop is quite old, or at least Intel thinks so, but > > > >emerging > > > >> chromium is now taking *much* longer than it ever did: > >A while back I accidentally broke the CPU throttling on my laptop, and > >it was always running at 1/4 speed. [That effected all emerges.] I'd > >start by doing a "grep MHz /proc/cpuinfo" during the build to verify > >that all the CPUs have open throttles. > > > >That said, I've noticed that Chromium in particular is taking a lot > >longer than it used to... > > I had similar issues with swapping on an 8GB laptop.. Limiting the numbers > of jobs helped but using jumbo-build more than halved the build time .
Interesting ... I had made a mental note to try out USE="jumbo-build". I'm not sure what pressure it will place on my limited resources, but the proof of the pudding ... I will give it a spin tomorrow, or whenever this emerge completes. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
