KInit - Current state and benchmarks
Milian Wolff
mail at milianw.de
Sat Nov 23 10:47:40 GMT 2019
On Mittwoch, 19. Juni 2019 19:57:56 CET Albert Astals Cid wrote:
> El dimarts, 18 de juny de 2019, a les 12:04:38 CEST, David Edmundson va
escriure:
> > > Are we sure it's fair to assume people have SSD? our of the 4 laptops i
> > > own, only 2 have SSD.>
> > It's at least safe to assume it's the trend moving forward.
> >
> > > Do you think it's worth me trying in one of the two that don't have SSD?
> >
> > More data is normally a good thing. If you or anyone else wants to
> > collect stats:
> > From my git link above, it's as simple as running the normal ; cmake;
> > make ; ./kinittest -median 5
>
> On my very old/very slow computer seems to make a lot of difference
>
> RESULT : DaveTest::testQProcess():
> 2,625 msecs per iteration (total: 2,625, iterations: 1)
> RESULT : DaveTest::testKInit():
> 1,852 msecs per iteration (total: 1,852, iterations: 1)
>
>
> RESULT : DaveTest::testQProcess():
> 2,390 msecs per iteration (total: 2,390, iterations: 1)
> RESULT : DaveTest::testKInit():
> 1,846 msecs per iteration (total: 1,846, iterations: 1)
Hey Albert,
these numbers are quite impressive but I can't quite explain those. Are you
measuring maybe a full debug build without any compiler optimizations? Then
the library sizes will be _much_ larger and thus trigger more page faults. If
every one of those is extremely slow on that machine compared to more modern
machines?
May I ask how old this machine is and what the speed of the HDD is?
Thanks
--
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20191123/5779fa74/attachment-0001.sig>
More information about the Kde-frameworks-devel
mailing list