My simple question is, would a Xeon Phi™ coprocessor be of any value in running asteroids@home, in its current state of 7.2.33? I have a little money to burn... No flaming please.

The short answer is probably No.

You'd have to get the source for the app and compile it to use the Phi. BOINC 7.2.33 has no support for the Phi however you can configure your own coprocessor if you want to treat it as such. Or you could (after creating your Phi app) treat them as CPU work unit and roll your own app_info to run them.

I will add they are working on a cuda GPU app so you may save your money and spend it on an Nvidia GPU. There is also an OpenCL app coming after the cuda one.

---

BOINC blog

We don't have even access to this architecture so for now you would have to compile the source codes yourself for Xeon Phi. The CUDA app is currently in testing, OpenCL may be sometime during the next year.

My simple question is, would a Xeon Phi™ coprocessor be of any value in running asteroids@home, in its current state of 7.2.33? I have a little money to burn... No flaming please.

I like Xeon Phi and this architecture should be good for our project. Windows are also supported (in past Linux only).

Porting app should be relatively easy, but we have no Xeon Phi here and it's not widely used by boinc volunteers so we decided to not focus on this hw.

Happy crunching and nVidia users stay tuned.

Zdenek

I have access to this architecture, and would be interested in porting it... however I do not know where to get the source code for asteroids@home. Do I just need the BOINC source?

I have access to this architecture, and would be interested in porting it... however I do not know where to get the source code for asteroids@home. Do I just need the BOINC source?

Projects write their own science apps. No it's not the BOINC code you need it's the science app. Send a private message to Kyong and/or HA Soft who should be able to help

---

BOINC blog

My simple question is, would a Xeon Phi™ coprocessor be of any value in running asteroids@home, in its current state of 7.2.33? I have a little money to burn... No flaming please.

You might talk to Slicker the Admin at Collatz, he mentioned the other day he was going to be 'working on it' when he had more time. He has been busy implementing the new Boinc capability of variable sized work units based on your systems capabilities, which is a part of that. All units have deadlines but if you send a unit to a Pi with a 1 year crunching time but a 2 week deadline there really is no point in it. As far as I know it is the first project to get it working, the Android units are MUCH smaller then the normal pc work units for instance, yet they all come from the same resource pile.