| 1 |
On 2015-11-10 14:07, Stanislav Nikolov wrote: |
| 2 |
> |
| 3 |
> On 11/10/2015 08:55 PM, Alan McKinnon wrote: |
| 4 |
>> On 10/11/2015 20:37, Stanislav Nikolov wrote: |
| 5 |
>>> On 11/10/2015 08:17 PM, Mick wrote: |
| 6 |
>>>> On Tuesday 10 Nov 2015 17:47:08 Stanislav Nikolov wrote: |
| 7 |
>>>>> Dear Gentoo users, |
| 8 |
>>>>> I'm building a new PC. I have a budget of ~$550-$650. |
| 9 |
>>>>> |
| 10 |
>>>>> <snip> |
| 11 |
>>>>> |
| 12 |
>>>>> The most expensive Intel CPU is the skylake i7-6700k. |
| 13 |
>>>>> |
| 14 |
>>>>> Thanks |
| 15 |
>>>> |
| 16 |
>> |
| 17 |
>> I can't help but think you are approaching this from the wrong perspective. |
| 18 |
>> |
| 19 |
>> Why exactly are you using compile times as your sole criterion? Are you |
| 20 |
>> building a compile farm for Ubuntu? Running continuous integration tests |
| 21 |
>> for LibreOffice [on a $600 budget in a cardboard box :-) ]? |
| 22 |
>> |
| 23 |
>> Or do you want emerge world to get it over with quicker? |
| 24 |
>> |
| 25 |
>> If the latter, you better rethink your priorities. In computing terms, |
| 26 |
>> compilation is a rare event; launching apps is a common event; and |
| 27 |
>> writing to the disk happens all the time. Optimize for the common case. |
| 28 |
|
| 29 |
In addition, upgrades are something that can be done overnight, or |
| 30 |
really any time you are not using the machine. |
| 31 |
|
| 32 |
>> |
| 33 |
>> A CPU never works in isolation, it is always part of a much larger |
| 34 |
>> system, like disks, RAM and all possible kinds of I/O. The best CPU on |
| 35 |
>> the market plugged into a POS motherboard will perform on emerge world |
| 36 |
>> like a piece of shit - it will follow the weakest link. |
| 37 |
|
| 38 |
This; I have an i7-3930K, which has 6 physical cores at 3.8GHz. I also |
| 39 |
have 32GB of RAM and an SSD. There was a large speedup[1] moving |
| 40 |
portage's workdir from SSD to tmpfs. Compiling is a really balanced |
| 41 |
workload, stressing the disk (multiple small reads), memory, and CPU. |
| 42 |
For fast compilation, emphasize RAM first (compile in tmpfs if |
| 43 |
possible), then CPU, then disk. Like Alan said, though, you should |
| 44 |
really optimize for the average case on not worry about the speed of |
| 45 |
compiling stuff. |
| 46 |
|
| 47 |
Alec |
| 48 |
|
| 49 |
1. It was a long time ago so I don't remember the exact numbers, but my |
| 50 |
firefox compiling time went from ~15 minutes to ~10 minutes after |
| 51 |
switching from SSD to tmpfs for portage's workdir. |
Archives