On 11/5/19 9:59 AM, Simon Richter wrote:
Hi,
I've made another quick run for Release builds:
MakeNinja
Scripting ON5:19.66 5:03.91
3336% 3565%
Scripting OFF 3:33.84 3:08.50
4947% 5684%
That is with -j64 on 2 socket T2P9D01.
You
Hi,
I've made another quick run for Release builds:
MakeNinja
Scripting ON5:19.66 5:03.91
3336% 3565%
Scripting OFF 3:33.84 3:08.50
4947% 5684%
That is with -j64 on 2 socket T2P9D01.
You can see that dependency generation makes
On 30/10/2019 17:37, Seth Hillbrand wrote:
>
> Two things can help there. First, using the gold linker (if you are not
> already) and second, using Ninja. The gold linker is substantially
> faster than the BFD linker.
I can confirm the above, way faster!
> And Ninja is smarter than make
On 2019-10-30 08:20, Simon Richter wrote:
That is more than 1100% CPU usage, with -j12, so very close to full
usage.
How is that even possible, don't you have that two minute phase at the
end
of building pcbnew_kiface where it's just building pcbnew_wrap.cxx.o
and
everything else is done?
On 30/10/2019 16:20, Simon Richter wrote:
> Hi,
>
> On Tue, Oct 29, 2019 at 07:00:48PM +0100, Tomasz Wlostowski wrote:
>
>> $ make -j12
>
>> real 7m59.758s
>> user 86m44.231s
>> sys 5m9.724s
>
> That is more than 1100% CPU usage, with -j12, so very close to full usage.
>
> How is that even
Hi,
On Tue, Oct 29, 2019 at 07:00:48PM +0100, Tomasz Wlostowski wrote:
> $ make -j12
> real 7m59.758s
> user 86m44.231s
> sys 5m9.724s
That is more than 1100% CPU usage, with -j12, so very close to full usage.
How is that even possible, don't you have that two minute phase at the end
of
I would have thought that any discussion of performance would have to take
the speed of the diskio into account
executing: (if you get command not found then install the sysstat package)
$iostat -h -x -d 2
whilst compiling would show the diskio utilization factor (last column), if
it is pegged
On 29/10/2019 15:40, Simon Richter wrote:
> We could probably shave off another two or three minutes of build time if
> we could make sure that we always make progress on the critical path. The
> dependency generation as a side effect pulls all the sources and headers
> into cache, which reduces
Ha, I also keep around my Thinkpad T61 for occasional testing for this
purpose, although usually I avoid building on it as that takes a lonng
time.
On Tue, Oct 29, 2019 at 10:57 AM Drew Van Zandt
wrote:
> Let me encourage some of y'all to stick with an older machine, or keep it
> around for
Let me encourage some of y'all to stick with an older machine, or keep it
around for testing... the latest build of KiCAD is noticeably laggy on my
machine, which is not terribly fast (but also not that old). It makes some
of the bugs I have reported worse, and their fixes have been pushed out to
Hi,
On Mon, Oct 28, 2019 at 10:20:45PM -0700, Andrew Lutsenko wrote:
> I kinda expected 2x maybe 3x decrease because not all computations scale
> linearly with number of threads. I was pleasantly surprised by almost 6x
> decrease in clean build time and 5x in incremental builds.
FWIW, we have a
Thanks for this data! I also have a Haswell system right now and have been
eyeing the new Ryzens... I too feel the pain of long kicad compilation
time.
-Jon
On Tue, Oct 29, 2019, 01:51 Henner Zeller wrote:
>
>
> On Mon, 28 Oct 2019 at 22:21, Andrew Lutsenko
> wrote:
>
>> Hi all,
>>
>> This
On Mon, 28 Oct 2019 at 22:21, Andrew Lutsenko wrote:
> Hi all,
>
> This information may be useful to people that are considering an upgrade
> for their workstations or for general information, feel free to skip this
> email if you are not interested.
>
> I've been using my 6 year old Haswell i7
Hi all,
This information may be useful to people that are considering an upgrade
for their workstations or for general information, feel free to skip this
email if you are not interested.
I've been using my 6 year old Haswell i7 machine that served me well over
the years but kicad compilation
14 matches
Mail list logo
