GPU Core update.

Soldato
Joined
16 Dec 2005
Posts
14,443
Location
Manchester
Just been browsing the Foldy forums and it turns out that tomorrow Stanford will be releasing a core update. From what I can gather your client will do this automatically when it comes across one of the new WUs that require the new version.

However, due to a crossed wire somewhere some of the new WUs were released a day or two early - should you get one of these WUs your client will get stuck moaning about an update that isn't available.

However, one of the guys who works on the client has posted a link for the new core in case anyone can't wait until tomorrow :D

FahCore_10.v7.zip

Just unzip it and put the file in your GPU client folder.

http://forum.folding-community.org/ftopic16503-0-asc-0.html

This is the link to the thread.

EDIT: This update also appears to cure the no-reporting bug AND checkpoints work again too :D

EDIT 2: Why did you keep this a secret eh, Mr Concorde?? Trying to get an advantage on us all? :p

SiriusB
 
Last edited:
LOL.

Heh, I have plans ;)

As for GPU V0.07, performance is up slightly, its updating the workunit % info so Fahmon etc can read it and finally its reporting what it should everywhere!
 
Yeah I noticed instant improvement. I think I have lost pretty much a whole day of GPU crunching at least due to the bugs found in the newer WUs. That's 660+ I'll never see again :(

Still, at least I can game again now without sacrificing an evenings work :D

SiriusB
 
That new client don't want to work for me. My GPU's been hung for the last couple of hours. Clearly doing nothing as the GPU temp hasn't risen.

Oh well, back to the CPU crunching.
 
Mine just finished its current WU and downloaded the new core automatically - no need to mess around now it would seem :)

edit:

[20:24:30]
[20:24:30] *------------------------------*
[20:24:30] Folding@Home GPU Core - Beta
[20:24:30] Version 0.07 (Wed Oct 18 04:38:38 PDT 2006)
[20:24:30]
[20:24:30] Compiler : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86
[20:24:30] Build host: CYGWIN_NT-5.1 vishal-gpu 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin
[20:24:30] Preparing to commence simulation
[20:24:30] - Assembly optimizations manually forced on.
[20:24:30] - Not checking prior termination.
[20:24:30] - Expanded 87036 -> 443705 (decompressed 509.7 percent)
[20:24:30]
[20:24:30] Project: 2711 (Run 0, Clone 13, Gen 5)
[20:24:30]
[20:24:30] Assembly optimizations on if available.
[20:24:30] Entering M.D.
[20:24:38] Starting GUI Server
[20:31:30] Completed 1
[20:38:11] Completed 2
:cool:
 
Last edited:
If you try to run 2 CPU clients and a GPU client, the GPU client will run as normal, getting around 600PPD by itself.

The two CPU clients however will be reduced to having only half a core each. Now, while you may be doing two WUs at a time, it will take twice as long.

Nothing wrong with this points wise as it would be very similar to just running 1 CPU client. However, the science prefers getting results sooner rather than later, so for the benefit of the science it is better to have just ONE CPU client running at full speed.

SiriusB
 
I prefer the 1 GPU and 1 CPU method on my X2, though I have both CPU clients services set to automatic so if the machine crashes and reboots for any reason it will revert to CPU clients only.

I haven't bothered testing the effect of 2 CPU clients and 1 GPU yet but as I only have 1GB RAM on this machine and large CPU WUs currently I wouldn't be left with much spare :o
 
I have 2GB of RAM on my machine so didn't notice much in the way of a performance hit on my system when I ran all three clients. However, I prefer running just the one CPU client as I get work done quicker.

I noticed when running all three clients that quite often the GPU client took up to 60% CPU, which leaves my CPU clients with less than half a core each, so I actually get more done overall as a result of running just one CPU client.

SiriusB
 
SiriusB said:
I noticed when running all three clients that quite often the GPU client took up to 60% CPU, which leaves my CPU clients with less than half a core each, so I actually get more done overall as a result of running just one CPU client.

SiriusB
I found the same when running 1 CPU client at "idle" and the GPU client at "low" - I've since set both to "low" and it won't go over 50% now :)
 
VeNT said:
ok downloading 6.10 drivers, installing GPU core client, will set it up tomorrow!

You'd be better off with the 6.5 drivers as 6.10 are still a bit flaky apparently.

6.5 definitely work, 6.10 may or may not work - I'm sticking to 6.5 until it is confirmed that 6.10 are working 100%.

Stan :)
 
Agreed, I tried for over an hour to get the GPU client working with the 6.10s with no joy.

The 6.5s are running perfectly - 22 completed WUs and counting :D

SiriusB
 
it says that it requires 6.10s?
oh well, 6.10s here already so I'll use them

any way to monitor the temp of my card? Speedfan doesn't do it!
 
VeNT said:
it says that it requires 6.10s?
oh well, 6.10s here already so I'll use them

Stanford GPU FAQ said:
Catalyst driver version 6.5 [download from ATI or from a Stanford mirror ]. Version 6.10 [see main ATI Folding@Home page or download driver from ATI ] with the newest core appears to be working now (but requires more testing to be sure). Versions 6.6 and 6.7 will work, but at a major performance hit; 6.8 and 6.9 will not work at all. Due to all the complexities of support, we will support only versions 6.5 and 6.10.

Taken from here

Stan :)
 
VeNT said:
it says that it requires 6.10s?
oh well, 6.10s here already so I'll use them

any way to monitor the temp of my card? Speedfan doesn't do it!
ATI tray tools - also good for locking the 3D speeds rather than the 2D speeds it will default to

see Conc's guide here

I'm using the 6.10s and they are working fine for me anyway :)
 
Managed to get it running X1950X-TX, using the 6.10 drivers. I don't think the 6.5 drivers work with this card?

It has completed a WU, but the system is very unresponsive to the mouse (E6600, @2.6Ghz - hardly pushing it) which dissapears the moment I stop the GPU client. 2 cores of CPU is just fine. Can only hope it gets sorted as a later fix otherwise the GPU client will only be running when I'm not using the PC.
 
Back
Top Bottom