1 |
On Wednesday, 5 December 2018 03:26:50 GMT Jack wrote: |
2 |
> On 2018.12.04 20:36, Adam Carter wrote: |
3 |
> > On Wed, Dec 5, 2018 at 7:41 AM Mick <michaelkintzios@×××××.com> wrote: |
4 |
> > > On Tuesday, 4 December 2018 19:23:27 GMT Jack wrote: |
5 |
> > > Phew! The chromium emerge completed with -j1, although it took 4 |
6 |
> > |
7 |
> > hours |
8 |
> > |
9 |
> > > longer |
10 |
> > > than last time on one PC and 6.5 hours longer on another. |
11 |
> > |
12 |
> > For those systems it might be worth trying the binary google-chrome |
13 |
> > instead. Much smaller download and; |
14 |
> > |
15 |
> > $ genlop -t google-chrome | tail -n3 |
16 |
> > |
17 |
> > Tue Nov 20 20:20:10 2018 >>> |
18 |
> > |
19 |
> > www-client/google-chrome-70.0.3538.110 |
20 |
> > |
21 |
> > merge time: 35 seconds. |
22 |
> |
23 |
> But only if you don't care about the differences between Chrome and |
24 |
> Chromium. They are close, but not (unless I'm terribly mistaken) |
25 |
> exactly the same. The latter is completely FOSS, but the former |
26 |
> contains some Google specific additions. While I do have both |
27 |
> installed, I don't particularly trust Google enough to use Chrome |
28 |
> unless nothing else works. It's pretty rare I need to use it. |
29 |
> |
30 |
> Jack |
31 |
|
32 |
I chose Chromium because I understood Google-Chrome to have some settings/ |
33 |
code, which is meant to link Google services with a user's footprint even |
34 |
after you have logged out of all Google services. |
35 |
|
36 |
What I found with Chromium is that it varies considerably on the amount of RAM |
37 |
consumed between versions, so it is a matter of guessing if 4G of RAM would be |
38 |
adequate to support > -j1. |
39 |
|
40 |
-- |
41 |
Regards, |
42 |
Mick |