16th of June

As you would have seen from the 2 previous blog posts I spent a bit of time last weekend testing the Adventure. I still can't find a case for it. Its currently packed away again until that gets sorted out. I can't believe nobody makes them over here in Australia, not even a custom built one!


BOINC news
In BOINC land they have been busy switching from using subversion to GIT, so nothing much new development wise.

I have asked for the GPU enumeration to be expanded as BOINC is currently limited to 8 devices but the drivers allow for 64. Dr Anderson has agreed to look into this. We can't stuff that many GPU's into a single machine but some people have managed to put more than 8 in a machine, even I can do that using the Adventure.


Farm news
I have ordered a couple of GTX670 cards which will be used to replace the GTX570's. The 570's will be up on eBay in about a week or so if anybody wants them. Hopefully GPUgrid will be releasing their CUDA 4.2 app to the mainstream fairly soon as it is still in beta testing.

I have been testing the x41x Seti GPU app from Jason G. Its built using CUDA 4.2 and seems to be faster than the older CUDA 3.2 x41g app. It also seems to be more reliable as I haven't seen any -12 errors that pop out from time to time with the older app. This also fits with future GPU upgrades as Kepler-based cards seem to need apps built using CUDA 4.2 to get the expected performance boost from having so many CUDA cores.

Crunching for the other projects continues. I have finished all the Climate Prediction work units that I had on various machines. They now are out of work. In the mean time Einstein is making steady progress, but I am yet to find a Pulsar.


GPU Users Group news
The GPUUG have got 2 current fund raisers going:

1. UPS - It consists of 6 x UPS and 5 x surge-protected power strips.
2. Green Bank data transport package. It consists of 3 x hard disk transport cases and 20 x 2Tb hard disk drives. A couple of the cases have already been supplied but they haven't raised enough for the hard disks yet.

Project news - Seti
In the last week or so Seti had a number of power issues to their building that resulted in one server "Thinman" and a couple of new work stations getting fried. This is why the GPUUG have started a UPS fund raiser.

Adventure testing (part 2)

So part 2 of this saga...

Yesterday I used one of the other P6T's to test with. Points to note:

1. It helps if you put the cards into the correct slot (start from the opposite end to the bridge card)
2. It likes to have a monitor plugged into the 1st card (the one nearest to the bridge card).

While opening and closing the case many times yesterday the hard disk in the machine died. Just as well I had recently put an SSD in there and backed up the hard disk before starting. Fortunately I have a couple of spare WD Caviar Blue drives I was going to upgrade machines with, but this one had a Caviar Black, well it did until it died yesterday.A quick instal of a new drive and copy the files back and it was up and running again with no work units lost.

Today its Maul's turn. You can see Maul being used with the Adventure and a single GTS450 SP at the bottom of the screen. The power supply is on the bottom right

Another shot of the Adventure and power supply sitting beside the P6T.

Here I have loaded up 4 of the GTS450 SP's into the Adventure

And just to see how it handles it another 2 GTS450 SP cards in the P6T as well

A screen shot of BOINC running a few work units on the GPU's

So this leads to an interesting thought, what if I were to get 2 Adventure's and plug both into one of the P6T's. Say 4 cards in each like I have done in this case, that would mean an 8 GPU machine is within possibility.

The GTS450 SP isn't a particularly powerful card. They are probably better running only a single task per GPU, but they only use one slot which means it can have some room either side for better air flow. They have also been superceeded by the newer Kepler-based cards.

Adventure testing (part 1)

This weekend is a long weekend, Monday is the Queens birthday public holiday. So I decided time to try getting the Adventure going, even though I don't have a case for it.

We start with Obi-Wan, the retired Jedi Knight I mean Acer Veriton V7900. Its an Intel Core2 Quad Q6600 machine with a single PCIe slot. Seeing as its retired I figured why not use it.

Next we have the old Corsair HX1000 power supply (1000 watts) which was also sitting around doing nothing. The bag is full of varous power cables as its a modular power supply.

And lastly we have the Adventure 2800 itself. The small board at the back is one of the bridge cards which the cable coming from the PC plugs into. 

After putting it together the 1st step was to see if it would power up without any add-in cards. This it did fine. There are a row of diagnostic LEDs on the front of the board that indicate it powered up.

The next step was to connect it to the PC. This bit also worked. However as soon as I added a graphics card to the Adventure the PC wouldn't boot. Probably something to do with the on-board Intel graphics and having an expansion board with a graphics card. Before anyone asks, I have run a couple of different graphics cards using the single PCIe expansion slot in it for a couple of years without any problems. Okay so it won't work with the Acer Veriton.

3rd of June

Not much to report this week. Crunching continues on the farm...


Project news - Einstein
They've discovered 9 new pulsars. 7 are in the Parkes data and 2 in the Arecibo data.

They are also sending out framed certificates to the users who find these new pulsars. Unfortunately I don't seem to have come across one.


Project news - GPUgrid
As mention last week they are beta testing new apps. It seems CUDA 4.0 will be the minimum version and CUDA 4.2 for the Fermi and Kepler based cards. All of the latest batch of CUDA 4.0 ones failed for me and a number of other users.


Project news - Seti
They were off-line for a few days while they repaired the faulty power cable on campus at UC Berkeley.

They also have a badly thought-out feature where they have limited reporting of work to 64 work units at a time. They introduced this limit as users get an "HTTP Internal Server Error" at some point, believed to be above 1000 work units. This has lead to much frustration as many machines have well over 64 work units to report, mine included. It also created another bug where it tries to resend some of the tasks as "lost tasks" even though they were just reported.