[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: state of the ’Pond for earnest tadpoles

From: James
Subject: Re: state of the ’Pond for earnest tadpoles
Date: Sat, 2 Jan 2021 15:19:50 +0000
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0


On 02/01/2021 14:07, Trevor wrote:

James wrote 02/01/2021 13:41:06
On 02/01/2021 12:20, Thomas Morley wrote:
A full `make doc` takes hours for me, even if invoked with `make doc
-j5 CPU_COUNT=5`
Thus I hardly do so, but use the CG-documented methods:
Perhaps 'an hour' if you were using some very, very old CPU - but even using a single CPU on an 'old' i5 Intel system a full make doc for me took less than 50 mins. That last time it took longer than an hour was when I had an old (8+ years ago) iMac running make doc in a linux VM.
When I had an old laptop with compromised cooling many years ago, a full build used to take several hours, presumably because my cpu was automatically clocked down to keep it from overheating. That was what triggered me to write the original versions (later improved by I forget who) of scripts/auxiliar/ MANUAL SECTION, as I was writing a lot of text for the manuals at the time, and needed to validate my contributions before pushing.

Right but that was 'many years ago' those scripts were there when I started (and that was ~2010), but even so, on 1 CPU, my Mother's old laptop (Dell circa 2014 - mid range i3 I think), doing a make doc took only 55 mins tops.

I understand that people might still have old hardware, but being worried that make doc takes 'hours' is no longer really true on any reasonable laptop hardware made within the last 5 or 6 years I'd say (using multiple Jobs or not to compile).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]