| 1 |
On Sun, Nov 20, 2016 at 9:48 AM, John Covici <covici@××××××××××.com> wrote: |
| 2 |
> On Sun, 20 Nov 2016 09:25:58 -0500, |
| 3 |
> Harry Putnam wrote: |
| 4 |
>> |
| 5 |
>> Rich Freeman <rich0@g.o> writes: |
| 6 |
>> |
| 7 |
>> > IMO over-committing CPU isn't actually THAT bad. The CPU obviously |
| 8 |
>> > gets divided n ways, but that's as far as it goes. There isn't that |
| 9 |
>> > much overhead switching between VMs (though there certainly is some). |
| 10 |
>> |
| 11 |
>> [...] |
| 12 |
>> |
| 13 |
>> Thanks for the fuller picture and putting in the time to write it. |
| 14 |
>> |
| 15 |
>> |
| 16 |
> |
| 17 |
> |
| 18 |
> On my i7 machine with 16g of ram, webkit-gtk has got to take 4/5 hours |
| 19 |
> to compile. This is using an ssd. |
| 20 |
> |
| 21 |
|
| 22 |
Are you building in a tmpfs? That would perform better than an ssd |
| 23 |
and would be much less wear on your flash besides. Of course, some |
| 24 |
packages do take a while to build. I don't notice as much now that I |
| 25 |
do most of my building from cron, but it can be painful when you have |
| 26 |
dependency chains or soname changes. |
| 27 |
|
| 28 |
-- |
| 29 |
Rich |
Archives