The BOINC server tries to work out which app is faster. It does that by trying a number of work units using each app. Once its got an idea how long they take it can then give you work for the fastest app.

I got some vanilla 101 as well as the SSE2 and SSE3 versions when the 101 app was first released. While they can be annoyingly slow (well the vanilla app was) if you just let them run the server will quickly work out what is best for your machine.

I don't understand why the Windows 64-bit and Linux 64-bit applications even have a vanilla version, as 64-bit CPUs have SSE2 at minimum. It would seem that the vanilla version could be removed and just go with the SSE2, SSE3, and AVX versions for 64-bit.

The BOINC server tries to work out which app is faster. It does that by trying a number of work units using each app. Once its got an idea how long they take it can then give you work for the fastest app.

I got some vanilla 101 as well as the SSE2 and SSE3 versions when the 101 app was first released. While they can be annoyingly slow (well the vanilla app was) if you just let them run the server will quickly work out what is best for your machine.

I don't understand why the Windows 64-bit and Linux 64-bit applications even have a vanilla version, as 64-bit CPUs have SSE2 at minimum. It would seem that the vanilla version could be removed and just go with the SSE2, SSE3, and AVX versions for 64-bit.

I also think that 64 bit world do not need standard app. Sse2 is always available.

The problem that the project owner has now is that now he has created super fast applications which complete work units much quicker, he is going to have to speed up work unit generation in order to keep up with the increased demand.

Kyong did mention he was going to look at larger work units once the enhanced apps were done.

---

BOINC blog