06 April 2014

6th of April

Farm news
Another warm week but overnight temperatures are falling so that I managed to get the Intel-GPU's going overnight. Its cool and wet today (Sunday) so I have also been running one of the GPUgrid machines.

The Intel-GPU crunchers have been mainly working on Climate Prediction ANZ work mixed with Asteroids. I find that the later BOINC version prefers to swap work out rather than splitting the resource shares. If I have 4 CPDN work units I would also like to run 4 Asteroids at the same time, however the 7.3.x works by running 8 Asteroids or trying to run 8 CPDN (except I have them limited to 4 concurrent). I raised this with the developers on the mailing list and was told they don't expect to fix it any time soon. That is the max_concurrent setting is partially ignored when scheduling what work to run.

I continue to get upload failures for some of the CPDN files. I resort to using the backup file/proxy server on the dial up to finish off the uploads for these. I also had one for GPUgrid this morning. I think its an ISP fault but they don't seem to have a clue. It only seems to happen on the big uploads (CPDN and GPUgrid have 12Mb plus result files) and even then some work fine and others repeatedly get stuck at the same point.


BOINC testing
We got 7.3.15 this week. which had a few minor tweaks since 7.3.11. They put a change into .14 to abort work that exceeded the memory limits and then decided to remove that change in .15 as it was aborting too much work (pretty much all projects seem to underestimate how much memory their work units need).

Collatz have said they were going to rewrite all their apps in COBOL, remove all optimisations and make only 32 bit apps to put everybody on an equal footing. This was of course an April fools day joke.


Pi work
Last week I tried to upgrade one of the Pi's from Debian Weezy (the current release) to Debian Jessie (the testing release) so I could get a more up to date BOINC client. The latest Jessie BOINC client is 7.2.42. So after adding the Jessie repo to my apt configuration file and then doing an "apt-get update" followed by "apt-get upgrade" it downloaded a heap of files and started installing until it ran into libcurl I think and then complained it was the wrong version. I couldn't get it past that so I had to restore the image I made before starting.

I am aware that Loctus of Borg also had a repo which has a few BOINC related things in there such as the BOINC client (without manager), BOINCtui and the Seti multi-beam app. It seems he has BOINC 7.2.33 so its not as up to date as the Debian Jessie version. The only other way to do it is get the source and compile my own version.

From reading the Raspberry Pi forums it looks like Debian Jessie is expected to get released some time in November 2014.

I had to re-image one of the Raspberry Pi's this weekend. The same Pi that I tried upgrading to Jessie the week before. I took a copy of one of the other Pi's that was working fine and then wrote that to the offending Pi's SD card. I then had to remove BOINC from it so it doesn't use the same computer Id and then reinstall from the repository. After that I reattached to the projects and merge the old and new computer Id's.

4 comments:

Stephen Maclagan said...

I have been running Jessie on the Pi for a few weeks now using the repository Boinc 7.2.42 and Manager,

a little known fact, the repository Seti 7.19 app is about twice the speed of the Daniel Carrion app, althrough still slow, about 6 and a half days for a Normal AR Wu at Stock Clock,
If you want a quick rundown of steps to compile Boinc PM me somewhere and i'll supply them.

Claggy

Stephen Maclagan said...

I have been running Jessie on the Pi for a few weeks now using the repository Boinc 7.2.42 and Manager,

a little known fact, the repository Seti 7.19 app is about twice the speed of the Daniel Carrion app, althrough still slow, about 6 and a half days for a Normal AR Wu at Stock Clock,
If you want a quick rundown of steps to compile Boinc PM me somewhere and i'll supply them.

Claggy

Mark G James said...

Hi Claggy, how did you upgrade to Debian Jessie? Did you do the same as I did or is there some other trick to it. Given I had to re-image it anyway it's possible that it was already corrupted which might be why the upgrade failed.

Stephen Maclagan said...

I followed this post:



http://www.raspberrypi.org/forums/viewtopic.php?p=522344#p522344



You have to update
/etc/apt/sources.list
change wheezy to Jessie.


I used a fresh install from NOOBS of Raspbian, I can't remember if I updated it, then I changed the sources.list entry,
there were lots of downloads, and it took some time to update,
and there was a least one warning about something being broken, and the check the installation suggested didn't reveal anything.

Claggy