20th of August

There was a bit of a delay in posting as I went away skiing last weekend, Here is the latest news:


BOINC testing
We're on 7.0.33 at the moment. There was a change to the FLOPS (floating point operations per second) estimate for GPU's which can cause issues if you upgrade while you stilll have GPU work. The estimate is now 10 times the CPU FLOPS as a default. Before it was set to the same value as the CPU. If you have existing work it will usually get an "estimated time limit exceeded" error. Its best to finish all GPU work before you upgrade to this version.


GPU Users Group
Terabit Systems donated some 10 Gbit networking gear to Seti@home. A big thank you to them for this equipment and the guys from the GPUUG for organising this. Comms within the server closet should improve quite a bit once this equipment has been installed.


Project news - CPDN
ClimatePrediction have now recreated most of their work units after their problems a fortnight ago. There are quite a few thousand work units available in the regional (EU or Pacific North West) series. They have had a few issues with filling the upload servers and then have to take it off-line for a couple of days while they make room.


Project news - Einstein
They have been updating their OpenCL app to give it improved speed.

They also had some network changes happening so appear as being off-line at random times during the week. The network changes are all over now so things are back to normal.


Project news - Seti
They had a problem with their version of the server code when they inadvertently removed references to CUDA work. This had the effect of running multiple instances of GPU work units (like 10 or 20) on pre version 7 BOINC clients. Newer BOINC clients worked fine, but those sticking with the old versions had the issue. In the newer clients its referred to as ATI or NVIDIA work. They have since fixed the issue.

In addition to that little problem they also had a 2 day outage due to scheduled electrical work in the Space Sciences Lab. That meant they were off-line for two days. After it came back on-line they weren't giving out GPU work while they worked though the CUDA issue. Its back to its totally maxxed-out 100 Mbit network connection at the moment.