<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 06/08/2018 17:19, Dennis Poon wrote:<br>
</div>
<blockquote type="cite"
cite="mid:98258114-571d-6269-8f82-9259c2eede4d@avidsoft.com.hk">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Martin wrote:<br>
<blockquote type="cite"
cite="mid:3509c91d-d9d7-fa0c-6124-8f69b2fc9043@mfriebe.de">On
06/08/2018 16:55, Dennis Poon wrote: <br>
<blockquote type="cite">The existing i3 uses DDR3 RAM and Core
i5 will come with DDR4 RAM. <br>
</blockquote>
Well check on userbenchmark what difference you can expect for a
single core benchmark. You can select the exact 2 cpu you are
interested in. <br>
<br>
That should give you are good indication. <br>
<br>
</blockquote>
Thanks a lot. <br>
There is the exact comparison<br>
<a class="moz-txt-link-freetext"
href="http://cpu.userbenchmark.com/Compare/Intel-Core-i5-8600K-vs-Intel-Core-i3-4130/3941vs1621"
moz-do-not-send="true">http://cpu.userbenchmark.com/Compare/Intel-Core-i5-8600K-vs-Intel-Core-i3-4130/3941vs1621</a><br>
<br>
<img src="cid:part2.B6BC3C47.FD2C72EF@mfriebe.de" alt="" class=""><br>
<br>
Should I look at the yellow region? it says average single core
speed is above 47% faster.<br>
</blockquote>
Yes, that line is single core benchmark<br>
<br>
From the help:<br>
<blockquote type="cite">Single core mixed speed is an important CPU
test for consumers. It measures the ability of a processor to
perform both integer and floating point operations at the same
time. This test only stresses one processing core at a time</blockquote>
<br>
FPC uses more parts of the cpu than the benchmark.<br>
So the value is indicative.<br>
<br>
So you *might* get 47%. It could even be a bit less than this. (to
be on the save side, I would expect less)<br>
<br>
Out of interest, how long does it take you to compile your project?<br>
<br>
To give you are comparison, on an i7-8700k, ssd, plenty of RAM, to
rebuild (clean) the IDE 1.8.4 / 64 bit / win 10<br>
without debug info, with -O2 takes 35 secs<br>
with debug info -gw, no opt takes 55 secs<br>
<br>
- this includes cleaning old files, with takes a few seconds in
itself<br>
- about half is building packages. (during this time, usually
several threads are active.)<br>
- only for 4 to 5 secs (of the 55 secs) all cores are fully used.
(so the 8600k should be close to the speed I got)<br>
<br>
You can check how long this takes on your current system. <br>
<br>
-----------------<br>
If you are compiling in the Lazarus IDE, there are a few things you
can do.<br>
<br>
I assume your project is rather big (otherwise compile time should
not really be the issue).<br>
<br>
You can move units to packages. They may not have to be compiled
each time, and if you move really lots to packages then they may be
compiled in parallel (though the main project probably will still
have the biggest chunk).<br>
<br>
Another factor in this is, that compiling with debug info is slower.
Using packages, you may compile some of them without debug info.<br>
<br>
And lastly, it is not just compiling.<br>
Starting the debugger takes some time too.<br>
2 ways to deal with this:<br>
- get the latest gdb. This may save a few percent.<br>
- in Lazarus trunk, use fpdebug (package LazDebuggerFp). This is a
good bit faster.<br>
<br>
<br>
</body>
</html>