I'm not advanced, but does somebody know the answere?

---

WARR - Wissenschaftliche Arbeitsgemeinschaft für Raketentechnik und Raumfahrt
(WARR - scientific working group for rocket technology and space travel)

Screen saver graphics use the OPEN GL engine

---

It's Out there........

IIRC, neither BOINC nor S@H official builds use the the extended features offered by MMX, 3DNow!, or SSE. Somebody may have created their own build utilizing one or more of these feature sets, but I haven't been paying enough attention to custom builds to know for sure.

---

i know that severall people are working on this...

a good Look is always here

http://www.ssl.berkeley.edu/pipermail/boinc_opt/2004-October/date.html

and severall people are working for an 64 bit Client, bus it is no so easy as it shows.

Greetings from Germany NRW
Ulli S@h Berkeley's Staff Friends Club m7 ©

I don't think so as compiling the source for the SETI client with these features enabled for athlonXP made virtually no difference to processing times compared to the standard seti client (about 1%).

Ned

---

*** My Guide to Compiling Optimised BOINC and SETI Clients ***
*** Download Optimised BOINC and SETI Clients for Linux Here ***

The issue is not just running the source code thru a compiler with some flags for 3DNow! or SSE. The code has to be completely rewritten to take advantage of these features and then compiled with those flags to see any benefit. That's a much more intensive task, and if it isn't done exactly right, the new code will produce WU results that differ slightly but significantly from those that are crunched with the vanila version.

---

Parts of it have been done, but not yet for official release.

SSE, 3DNow versions of several functions are written and cross verify with unmodified client 4.05 and 4.03 seti WUs (on validator).

---

Thx for the huge amount of answers!

---

WARR - Wissenschaftliche Arbeitsgemeinschaft für Raketentechnik und Raumfahrt
(WARR - scientific working group for rocket technology and space travel)