Zajimavy prispevek na E@H foru pridal
Offic. app. je optimalizovana pro SSE instrukce. To, jestli se SSE pouzivaji najdete v resultu te dane WU.
"Detected CPU type" 1 - SSE nebo 0 - non SSE (generic x86)
Akos spolu s nim pracuji na dalsich (3Dnow!, SSE3) variantach.
Takze zadna optimalizace mimo E@H projekt od Akose nebude, vsechny budou primu v offic. app. Tim odpada neustale hlidani a rucni (prip. BS) update.
Lepsi zprava uz snad ani nemohla prijit. Kez by se touto cestou vydali i ostatni projekty.
OT: Vzpominate nekdo na minibenchmark a pouziti ruznych core u distributed.net? ;-)
EDIT: Ted se snazim cist tu orig. zpravu uz asi 5x dokola a nejsem si jistej, jestli jsem vystihl zneni te msg. tak mi anglictinari kdyztak opravte.
EDIT2: Nevim proc ten odkaz prestal fungovat kdyz v historii msg od nej je, tak to sem pastnu:
[quote="Bernd Machenschalk"]The current (x86-) Apps do incorpoarate specific optimizations for SSE, they do detect the CPU they're running on and will choose to execute code for this specific CPU. However this distinction is currently only made between SSE and non-SSE CPUs. You will find a line in the stderr output of your results that reflects this: "Detected CPU type" - 1 means SSE, 0 means generic.
We (Akos and I) will continue to work on speeding up the Apps. This will probably include code for more CPU variants (3Dnow!, SSE3). Some things that are advantagous for one or the other CPU type may be hard to incorporate in an App that switches CPU types, e.g. instruction order and code alignment, such that the switching doesn't eat up all the speed gained, but I think there are quite some things left to try.
IMHO reporting a more detailed platform from the client to the project would lead to the possibility of distributing faster Apps. Some discussion about that has started on the BOINC devleopers mailing list, but that's quite a way to go until that would be implemented and can be benificial to the projects.
Akos isn't working exclusively for Einstein@Home and I have also been busy with preparing, implementing and testing the S5R1 setup, and will probably continue to be the next one or two weeks to iron out the last issues that arise. So the "science code" that determines the speed of the Apps is currently freezed.
Naposledy upravil(a) Bubak
dne úte čer 20, 2006 2:01 pm, celkem upraveno 1 x.
[url=http://www.boincstats.com/signature/user_335804.gif]Private (old)[/url] + [url=http://www.boincstats.com/signature/user_769641.gif]CCU[/url] stats.