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