These are the last two I picked up today,

2246323 1416677 30 Apr 2010 12:14:27 UTC 30 Apr 2010 13:00:35 UTC Completed and validated 1,684.90 198.56 187.28 280.92 ACEMD beta version v6.22 (cuda)
2246484 1416768 30 Apr 2010 13:12:52 UTC 30 Apr 2010 13:37:52 UTC Completed and validated 731.35 713.28 187.28 280.92 ACEMD beta version v6.23 (cuda30)

Looks like they just started up again :-)

---

Thanks - Steve

I have been trying to work out why this GTX470 is slower than it should be. (0.81)

Unfortunately I messed this Beta up, when I changed some timings using MSI Afterburner.
2247794 1417527 30 Apr 2010 18:59:09 UTC 30 Apr 2010 19:02:25 UTC Error while computing 77.60 71.07 187.28 --- ACEMD beta version v6.23 (cuda30)

I did manage to increase the Boinc rating to 945 GFLOPS peak, but for some reason it only lets me turn the shaders up from 810MHz to 1055MHz!

Any ideas?

The Fermi Beta tasks seem to be working well.

I think some crapware that came with this Asus card might be to blame for the shader clock speeds, though I suspect having Boinc 6.10.18 to begin with did not help either, as it was reporting about 110GFlops peak.
Boinc/GPUGrid now sees the shaders as being what they should be at, as does GPU-Z, but I did have to use EVGA Precision to set the shaders to what they should be!

You might want to note that the task run time length is just the same however! So either the shader speed was just a reporting issue and W7 is much slower than XP with Fermi's or I still have a problem;

Recent task
Run time 743.539049
CPU time 714.313
stderr out

<core_client_version>6.10.50</core_client_version>
<![CDATA[
<stderr_txt>
# Using device 0
# There is 1 device supporting CUDA
# Device 0: "GeForce GTX 470"
# Clock rate: 1.30 GHz
# Total amount of global memory: 1309081600 bytes
# Number of multiprocessors: 14
# Number of cores: 112
MDIO ERROR: cannot open file "restart.coor"
# Time per step (avg over 50000 steps): 14.815 ms
# Approximate elapsed time for entire WU: 740.739 s
called boinc_finish

</stderr_txt>
]]>

earlier task
Run time 740.302343
CPU time 719.539
stderr out

<core_client_version>6.10.50</core_client_version>
<![CDATA[
<stderr_txt>
# Using device 0
# There is 1 device supporting CUDA
# Device 0: "GeForce GTX 470"
# Clock rate: 0.81 GHz
# Total amount of global memory: 1309081600 bytes
# Number of multiprocessors: 14
# Number of cores: 112
MDIO ERROR: cannot open file "restart.coor"
# Time per step (avg over 50000 steps): 14.753 ms
# Approximate elapsed time for entire WU: 737.672 s
called boinc_finish

</stderr_txt>
]]>

Boinc is still reporting the wrong number of processors and cores. Put 6.10.45 back on, same situation.

Did some task suspends, shutdowns and clocked the GTX470 to that of a GTX480 without any issues.
Saw some speed increase in doing so, but GPU load fell from 65% to 60%
GPU 63 deg C, fan at 73% for above.

I have been trying to get the ACEMD beta to download tasks and it keeps telling me it is unavailable. I've tried this on 6 different occasions over the last 2 days. I hope more ACEMD beta work units become available soon and in greater number.

I've got 2 480 GTX cards ready to crunch!

Just select to do Beta work Only; no other tasks, and try again.
You are picking up other work units that wont work on Fermi.

There are plenty right now!

So after doing some math my OC GTX480 is averaging 32-33k PPD what are the chances that will improve in the near future? What is a single GTX295 averaging these days?

>Just select to do Beta work Only; no other tasks, and try again.

Just remind also to check "Run test application?" to yes.

After updating systemlines (twice) with swan_sync=0 (windows xp-pro)
cpu use stays on 0.21 cpu + 1 nvidia (after restarting boinc 06.10.50).

Correct?

Last two beta WU last night within 6 min 30 secs without changing systemlines!

---

Ton (ftpd) Netherlands

Look at the CPU time reported by your last task compared to earlier ones.

How do you change the cpu usage? Right now its at 0.11 cpu

After updating systemlines (twice) with swan_sync=0 (windows xp-pro)
cpu use stays on 0.21 cpu + 1 nvidia (after restarting boinc 06.10.50).

Correct?

Last two beta WU last night within 6 min 30 secs without changing systemlines!

You are almost at the right speed.
# Time per step (avg over 50000 steps): 7.366 ms
It could be that the low priority is making impossible to get to top speedwith this small molecular system or that Windows is slower than Linux. I will submit on Monday something bigger.

gdf

Last beta WU this morning # 63 = 6 min 25 secs, including changing systemfiles.

Better now?

Nice weekend!

---

Ton (ftpd) Netherlands

@sk: 400 MHz core and 800 MHz shaders sounds like a power saving mode to me. Weren't there problems before that some cards didn't wake up from 2D power saving mode properly? Not sure which tool would display the correct clock in real time, though.

MrS

---

Scanning for our furry friends since Jan 2002

I guess there are a mixture of problems:
Firstly, you are right; it is defaulting to a reduced speed, but I cannot be sure exactly what is dropping and by how much, the tools are not reliable! I have to use a number of tweaking tools to get it to read and change the clock speeds correctly, not easy. Actually, I still have my doubts about any of the readings - it may not actually be doing what it says it is doing, or perhaps only partially or intermittently. My return times are still too far out from what they should be.

GPUZ shows that the GPU rates can actually drop more than once. Right down to the following (at present settings),
- GPU core clock - 50.5MHz (normal 608MHz), (OC 707MHz)
- GPU mem clock - 67.5MHz (normal 837MHz), (OC 863MHz times two, I hope)!
- GPU shader clock - 101.0MHz (normal 1215MHz), (OC 1414MHz)

I noticed the memory controller load remains at 9% when the card is doing next to nothing!

The other issues could be to do with the Asus tweaking app that came with it, the OS (Win7 x64), drivers, or Boinc versions. We know Linux is faster, and XP is slightly faster too, so it is hard to say what is going on.
Anyway, when I have time I will put it into an XP system, or a server - perhaps Mon/Tue.
For now I will let it run some Betas, and report back. Perhaps in a few days there will be updates to the tools, drivers and Boinc! Perhaps the drivers already work better on XP than W7.

How do you change the cpu usage? Right now its at 0.11 cpu

If you already have the SWAN_SYNC environmental variable set to 0 then it should be using a full thread but BOINC still reports the percentage use just like if you did not have the eniron set. To double check open task manager and take a look ... when I first open it acemdbeta_* is reporting a small percent 0-3 use but if I wait cople seconds it will jump up to a full thread being used. My guess it that it is working properly but BOINC does not bother updating after the task is started (the acemdbeta has not yet initialised full thread) and Task Manager caches the initial value (like BOINC) but after it refreshes it reports correctly.

---

Thanks - Steve

@sk: BOINC hardly knows what a GPU is. There's no way it could alter its clock speeds and / or power saving settings. It just calls the executeable (GPU-Grid app). The memory clocks are OK, though: multiply them by 4 and you get the "advertising numbers". My HD4870 normally runs the mem at 900 real-MHz = 3600 marketing-MHz. And a memory controller load of 9% might be OK for 67 MHz. The desktop is in a frame buffer in GPU mem and needs to be read / updated according to the display refresh rate. 9% does sound high for such load, but who knows what else is going on..
To check the clock speeds you could use the artefact tester of some of the nice tools. Set it to display a static image, watch the FPS and adjust the clocks. Should be a nice feedback since it's a windowed application.

MrS

---

Scanning for our furry friends since Jan 2002

We know Linux is faster, and XP is slightly faster too,

SK, XP32 and XP64 are quite a bit faster than either Win 7 32 or 64 for GPUGRID. Nothing has changed in the newer GPUGRID versions. I've been monitoring the times hoping the problem would be fixed. It hasn't been.

The relative speeds are still as described in this thread:

http://www.gpugrid.net/forum_thread.php?id=1729

And before that, here:

http://www.gpugrid.net/forum_thread.php?id=1449

We are going way off topic here but, Beyond, I'll quote you,

when I switched from XP-64 to W7-64, compute time went up from 27k to 30k per WU

OK, so you found an 11% or 12% difference, even with Aero off and W7 largely optimized for crunching GPUGrid tasks. I found less, when I last looked, but either way I think it is reasonable to say there is a slight difference between XP and vista/W7, as I also mentioned a big difference with Linux (35% faster, or something like that) - semantics.
I still think some of this is down to the CPU usage of GPUGrid WU’s being slower under W7 than XP; after all it has to make that blue circle go round ;). Perhaps the Environmental Variable (SWAN_SYNC=0) will reduce some of this difference or an app update could (given that Vista/W7 are not any slower on other GPU projects).

Who knows, when a Fermi app is optimized and released it might not make any difference if we use XP or Vista.

>Just select to do Beta work Only; no other tasks, and try again.

Just remind also to check "Run test application?" to yes.

Thank you! I already selected only to run the ACEMD beta but didn't know that "Run test application" had to be switched to yes. That did the trick and I'm now downloading beta work units for my 480 GTX!