If the V7 GPU app's are doing more Intensive work on the Wu's , is it maybe more needed to free up 1 core on cpu , to be more effective for GPU work ?
With the V6 apps , I was getting about the same results with one core free as I was without one free, as far as credit and time went anyway.

Cuda apps under V7 'shouldn't' be using more CPU. Juan tested this earlier & reported no difference with or without freeing CPU cores, with multiple tasks per GPU. The extra intensive work is taxing on the GPU memory system.

This extra search processing (Autocorrelations) will tend to limit the optimal number of tasks run simultaneously per GPU, to a lower figure, and run somewhat cooler. and of course more work takes longer ;)

No idea where Credits will settle.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I found the first host getting ATI V7 work with unsupported drivers.
He is running Cat 11.11 SDK 2.5 while SDK 2.6 is required.


http://setiathome.berkeley.edu/results.php?hostid=6766783

I have 2 wingmates so far that seem to be running sdk 2.5. Hope this isnt going to be the new enviroment variable thing! :)

---

Isn't is possible to download stock v7 CPU app and put it in app_info.xml ?

sure it's possible.
We just hope to provide faster app at Monday.
For now stock v7 CPU could go.

What's the URL for stock app then? (until monday)

You would need, as a minimum,

http://boinc2.ssl.berkeley.edu/sah/download_fanout/setiathome_7.00_windows_intelx86.exe
http://boinc2.ssl.berkeley.edu/sah/download_fanout/libfftw3f-3-3_upx.dll

I've deliberately not made them clickable, because I want casual readers to stop and think before downloading.

The file sizes are 484,352 and 1,049,920 bytes respectively. Internet Explorer seems to have a habit of truncating manual downloads: Chrome seems better.

Thanks works fine it seems. DL with Chrome with no probs.

Cuda apps under V7 'shouldn't' be using more CPU. Juan tested this earlier & reported no difference with or without freeing CPU cores, with multiple tasks per GPU. The extra intensive work is taxing on the GPU memory system.

Just a remainder i only have INTEL CPUs and Fermis/Kepplers GPUs.

And in all the test i mantain only 2 WU crunching (1 or 2 Vlars at the same time on each GPU)at a time to avoid video lag.

---

Isn't is possible to download stock v7 CPU app and put it in app_info.xml ?

sure it's possible.
We just hope to provide faster app at Monday.
For now stock v7 CPU could go.

What's the URL for stock app then? (until monday)

You would need, as a minimum,

http://boinc2.ssl.berkeley.edu/sah/download_fanout/setiathome_7.00_windows_intelx86.exe
http://boinc2.ssl.berkeley.edu/sah/download_fanout/libfftw3f-3-3_upx.dll

I've deliberately not made them clickable, because I want casual readers to stop and think before downloading.

The file sizes are 484,352 and 1,049,920 bytes respectively. Internet Explorer seems to have a habit of truncating manual downloads: Chrome seems better.

Thanks works fine it seems. DL with Chrome with no probs.

In response to an enquiry by PM: the stock CPU app, as usual, can display eye candy or a screensaver. For that, you need

http://boinc2.ssl.berkeley.edu/sah/download_fanout/setigraphics_7.00_windows_intelx86.exe

As most of my machines have 7 or 8 day caches with 100 tasks, & are downloading resends, I don't expect to run out of work before the next lunatics release.
Perhaps some of my faster machines will run out & flip over to PrimeGrid for a bit, but that is OK with me. Keeps the details page on my machines from getting junked up with stock app info.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Well, my first v7 has started. Estimated 15h 15m. We'll see.
I went and edited my app_info.xml, included the new app by hand.

30-May-2013 22:12:30 [SETI@home] Starting task 27no10ad.29489.21917.6.12.77_1 using setiathome_v7 version 700 in slot 0

---

I just noticed something that I don't remember seeing on the V6 WU's for GPU.

On PC ( #1 ) 5953062 the GPU wu is showing " Running ( 0.0236 CPU's + 1 NVidia GPU )" CUDA 32 WU

On PC ( #2 ) 6994641 the GPU wu is showing " Running ( 0.00579 CPU's + 1 NVidia GPU )" CUDA 42 WU

The difference in CPU usage... Can this be because of the different Video cards ?

#1 has the GTX 460SE and #2 has the GT 430 .

OR
because of the different Cuda apps being used at this time ?

---

Have now taken to manually aborting:
-AP WUs on non AVX machines
-v7 cuda50 WUs on all machines
-v7 cuda23 WUs on all GTX580 based machines

---

I'm just having a large missed deadline v7 gpu wu's, yet no deadline that I looked at is earlier than 6/19/2013, I used to get the occasional one under v6, but that was it. Why?

SETI@home 7.00 setiathome_v7 (cuda42) 26jn12ab.17393.3343.15.12.234_1 00:14:31 (00:02:10) 5/30/2013 3:43:49 PM 5/30/2013 3:43:49 PM 0.05C + 0.5NV 14.93 Missed
SETI@home 7.00 setiathome_v7 (cuda42) 26mr10ab.31337.1466.10.12.214_3 00:17:33 (00:02:13) 5/30/2013 3:36:37 PM 5/30/2013 3:36:37 PM 0.05C + 0.5NV 12.63 Missed
SETI@home 7.00 setiathome_v7 (cuda42) 26mr10ab.16506.4979.13.12.200_0 00:17:54 (00:02:16) 5/30/2013 3:25:47 PM 5/30/2013 3:29:09 PM 0.05C + 0.5NV 12.66 Reported: OK
SETI@home 7.00 setiathome_v7 (cuda42) 23jn12ab.21127.12341.15.12.184_3 00:06:58 (00:01:24) 5/30/2013 3:23:47 PM 5/30/2013 3:23:47 PM 0.05C + 0.5NV 20.10 Missed
SETI@home 7.00 setiathome_v7 (cuda42) 26oc12ac.27301.375686.8.12.18_0 00:12:47 (00:01:46) 5/30/2013 3:06:38 PM 5/30/2013 3:14:03 PM 0.05C + 0.5NV 13.82 Reported: OK
SETI@home 7.00 setiathome_v7 (cuda42) 26jn12ab.17393.2116.15.12.140_1 00:18:33 (00:02:17) 5/30/2013 3:03:37 PM 5/30/2013 3:03:37 PM 0.05C + 0.33NV 12.31 Missed
SETI@home 7.00 setiathome_v7 (cuda42) 26mr10ab.16506.3752.13.12.79_1 00:17:33 (00:02:15) 5/30/2013 3:03:37 PM 5/30/2013 3:03:37 PM 0.05C + 0.33NV 12.82 Missed
SETI@home 6.03 setiathome_enhanced 20jn12ab.5754.24299.5.11.56_0 00:24:48 (00:23:32) 5/30/2013 2:51:27 PM 5/30/2013 2:57:29 PM 94.89 Reported: OK
SETI@home 7.00 setiathome_v7 (cuda42) 26oc12ac.27301.375686.8.12.17_1 00:14:34 (00:01:45) 5/30/2013 2:49:23 PM 5/30/2013 2:49:23 PM 0.05C + 0.33NV 12.01 Missed
SETI@home 7.00 setiathome_v7 (cuda42) 26jn12ab.17393.2116.15.12.143_1 00:21:51 (00:02:29) 5/30/2013 2:45:25 PM 5/30/2013 2:49:23 PM 0.05C + 0.33NV 11.37 Reported: OK
SETI@home 7.00 setiathome_v7 (cuda42) 26jn12ab.17393.2116.15.12.127_0 00:21:31 (00:02:28) 5/30/2013 2:43:25 PM 5/30/2013 2:45:25 PM 0.05C + 0.33NV 11.46 Reported: OK
SETI@home 6.03 setiathome_enhanced 17au10aa.25434.76667.4.11.32_1 01:29:24 (01:24:37) 5/30/2013 2:33:23 PM 5/30/2013 2:35:25 PM 94.65 Reported: OK *
SETI@home 7.00 setiathome_v7 (cuda42) 26jn12ab.17393.2116.15.12.188_1 00:18:25 (00:02:20) 5/30/2013 2:32:59 PM 5/30/2013 2:35:25 PM 0.05C + 0.33NV 12.67 Reported: OK
SETI@home 6.03 setiathome_enhanced 17au10aa.25434.76667.4.11.245_0 01:29:41 (01:24:48) 5/30/2013 2:26:38 PM 5/30/2013 2:31:36 PM 94.55 Reported: OK
SETI@home 7.00 setiathome_v7 (cuda42) 26oc12ac.27301.375686.8.12.31_0 00:13:42 (00:01:39) 5/30/2013 2:23:22 PM 5/30/2013 2:25:25 PM 0.05C + 0.33NV 12.04 Reported: OK
SETI@home 7.00 setiathome_v7 (cuda42) 26oc12ac.27301.375686.8.12.16_0 00:13:01 (00:01:42) 5/30/2013 2:23:22 PM 5/30/2013 2:25:25 PM 0.05C + 0.33NV 13.06 Reported: OK
SETI@home 6.03 setiathome_enhanced 17au10aa.25434.76667.4.11.37_0 01:29:31 (01:24:39) 5/30/2013 2:19:25 PM 5/30/2013 2:25:25 PM 94.56 Reported: OK
SETI@home 7.00 setiathome_v7 (cuda42) 26mr10ab.16506.2934.13.12.76_1 00:21:44 (00:02:20) 5/30/2013 2:14:38 PM 5/30/2013 2:19:25 PM 0.05C + 0.33NV 10.74 Reported: OK
SETI@home 7.00 setiathome_v7 (cuda42) 26jn12ab.25709.12346.13.12.252_2 00:21:00 (00:02:18) 5/30/2013 2:09:55 PM 5/30/2013 2:09:55 PM 0.05C + 0.33NV 10.95 Missed
SETI@home 7.00 setiathome_v7 (cuda42) 26mr10ab.16506.2934.13.12.50_0 00:20:36 (00:02:16) 5/30/2013 2:09:55 PM 5/30/2013 2:13:55 PM 0.05C + 0.33NV 11.00 Reported: OK *
SETI@home 7.00 setiathome_v7 (cuda42) 26jn12ab.17393.1298.15.12.74_0 00:15:38 (00:01:43) 5/30/2013 1:53:38 PM 5/30/2013 1:57:38 PM 0.05C + 0.33NV 10.98 Reported: OK
SETI@home 7.00 setiathome_v7 (cuda42) 26mr10ab.16506.2934.13.12.150_1 00:22:38 (00:02:23) 5/30/2013 1:49:38 PM 5/30/2013 1:53:38 PM 0.05C + 0.33NV 10.53 Reported: OK
SETI@home 7.00 setiathome_v7 (cuda42) 26mr10ab.16506.2934.13.12.74_0 00:20:28 (00:02:19) 5/30/2013 1:47:38 PM 5/30/2013 1:47:38 PM 0.05C + 0.33NV 11.32 Missed
SETI@home 7.00 setiathome_v7 (cuda42) 26mr10ab.16506.2934.13.12.54_0 00:15:22 (00:02:11) 5/30/2013 1:38:14 PM 5/30/2013 1:38:14 PM 0.05C + 0.5NV 14.21 Missed
SETI@home 7.00 setiathome_v7 (cuda42) 27jl12af.30185.2689.6.12.44_1 00:08:23 (00:01:37) 5/30/2013 1:27:30 PM 5/30/2013 1:31:30 PM 0.05C + 0.5NV 19.28 Reported: OK
SETI@home 7.00 setiathome_v7 (cuda42) 26oc12ac.27301.44103.8.12.75_0 00:09:55 (00:01:36) 5/30/2013 1:20:14 PM 5/30/2013 1:22:36 PM 0.05C + 0.5NV 16.13 Reported: OK
SETI@home 7.00 setiathome_v7 (cuda42) 26mr10ab.16506.2934.13.12.155_0 00:11:23 (00:02:14) 5/30/2013 1:18:12 PM 5/30/2013 1:18:12 PM 0.05C + 0.5NV 19.62 Missed

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

Have now taken to manually aborting:
-AP WUs on non AVX machines
-v7 cuda50 WUs on all machines
-v7 cuda23 WUs on all GTX580 based machines

Why?

Have now taken to manually aborting:
-AP WUs on non AVX machines
-v7 cuda50 WUs on all machines
-v7 cuda23 WUs on all GTX580 based machines

When I checked, you were aborting v7 cuda23 tasks on your GTX 295 host, not your GTX580 hosts, and if you were then there would be a scheduler Bug because the Cuda23 Can't be run on Fermi's and Keplers.

Claggy

Before we switched to v7 we had a shorties storm, is that one still raging in v7?

Hadn't noticed anything before the outage.
Till i can get these executables to download no way of knowing myself- i doubt it as the splitters don't apear to be splitting much, and there's no ready-to-send buffer.

The Server Status Page section on Database/File Status does not yet reflect V7 task generation, only Enhanced V6, which are no longer being split. We saw the same thing when they rolled out Astropulse V6. Until almost all S@H V6 work is returned and validated, they will not change the display to reflect V7 production.

Looks like they went ahead and updated the Server Status Page so the Splitter Status Table reflects V7 production. That will make a few people less unhappy.

---

Donald
Infernal Optimist / Submariner, retired

Vic wrote:
]

I'm just having a large missed deadline v7 gpu wu's, yet no deadline that I looked at is earlier than 6/19/2013, I used to get the occasional one under v6, but that was it. Why?

SETI@home 7.00 setiathome_v7 (cuda42) 26jn12ab.17393.3343.15.12.234_1 00:14:31 (00:02:10) 5/30/2013 3:43:49 PM 5/30/2013 3:43:49 PM 0.05C + 0.5NV 14.93 Missed
SETI@home 7.00 setiathome_v7 (cuda42) 26mr10ab.31337.1466.10.12.214_3 00:17:33 (00:02:13) 5/30/2013 3:36:37 PM 5/30/2013 3:36:37 PM 0.05C + 0.5NV 12.63 Missed
SETI@home 7.00 setiathome_v7 (cuda42) 26mr10ab.16506.4979.13.12.200_0 00:17:54 (00:02:16) 5/30/2013 3:25:47 PM 5/30/2013 3:29:09 PM 0.05C + 0.5NV 12.66 Reported: OK

Looks like a BoincTasks History tab. The "missed" doesn't refer to deadline, just that BoincTasks missed picking up the information when BOINC reported the task completion. You'll probably find those tasks in your pendings or validated - you don't show any expired for deadlines. Don't know why BT is missing so many. it always misses a few a day but this is unusual. I haven't had that problem with my first 100 V7 tasks and BT 1.46, so if it continues, take it up with Fred in his forum.

---

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

Vic wrote:
]

I'm just having a large missed deadline v7 gpu wu's, yet no deadline that I looked at is earlier than 6/19/2013, I used to get the occasional one under v6, but that was it. Why?

SETI@home 7.00 setiathome_v7 (cuda42) 26jn12ab.17393.3343.15.12.234_1 00:14:31 (00:02:10) 5/30/2013 3:43:49 PM 5/30/2013 3:43:49 PM 0.05C + 0.5NV 14.93 Missed
SETI@home 7.00 setiathome_v7 (cuda42) 26mr10ab.31337.1466.10.12.214_3 00:17:33 (00:02:13) 5/30/2013 3:36:37 PM 5/30/2013 3:36:37 PM 0.05C + 0.5NV 12.63 Missed
SETI@home 7.00 setiathome_v7 (cuda42) 26mr10ab.16506.4979.13.12.200_0 00:17:54 (00:02:16) 5/30/2013 3:25:47 PM 5/30/2013 3:29:09 PM 0.05C + 0.5NV 12.66 Reported: OK

Looks like a BoincTasks History tab. The "missed" doesn't refer to deadline, just that BoincTasks missed picking up the information when BOINC reported the task completion. You'll probably find those tasks in your pendings or validated - you don't show any expired for deadlines. Don't know why BT is missing so many. it always misses a few a day but this is unusual. I haven't had that problem with my first 100 V7 tasks and BT 1.46, so if it continues, take it up with Fred in his forum.

Yeah, It is BoincTasks 1.47...

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

Well I wasn't going to do anything until next week, but I got bored.

The GTX 550Ti's on my 2500K are now running V7 and so far so good.

If it stays that way then tomorrow or the day after I'll do the same with the GTX 660's on my Q6600.

Cheers.

Well I wasn't going to do anything until next week, but I got bored.

The GTX 550Ti's on my 2500K are now running V7 and so far so good.

If it stays that way then tomorrow or the day after I'll do the same with the GTX 660's on my Q6600.

Cheers.

Enjoy the ride ...

L.

---

Have now taken to manually aborting:
-AP WUs on non AVX machines
-v7 cuda50 WUs on all machines
-v7 cuda23 WUs on all GTX580 based machines

When I checked, you were aborting v7 cuda23 tasks on your GTX 295 host, not your GTX580 hosts, and if you were then there would be a scheduler Bug because the Cuda23 Can't be run on Fermi's and Keplers.

Claggy

Richard, Claggy

AP:
I only run AP on the i7 with the CPU. I don't run AP on the GPUs in this box and I don't run AP on any of the other boxes (CPU or GPU).

MB:
v7 cuda50 was taking circa 80 minutes to run on the 295s. Far to long, so any cuda50 WUs landing here get aborted.

v7 cuda50 wus landing on any of the 580s also get aborted. The ones that have landed here and I have seen seem to have an exponential processing time albiet not as bad as the 295s. I must say that since implementing this practice the number of cuda50 WUs landing on these GPUs is declining to almost being non existent.

v7 cuda23 wus landed on the Q6600 with dual GTX580s. These appeared to be going down the same path as the cuda50 so they were aborted.

The 295s are now running cuda32 and cuda42 WUs for the GPU.
One of the 580s is running only cuda42 WUs at present, the other is running cuda32 and cuda42 WUs at present (just burnt another cuda50 WU there).

---

Have now taken to manually aborting:
-AP WUs on non AVX machines
-v7 cuda50 WUs on all machines
-v7 cuda23 WUs on all GTX580 based machines

When I checked, you were aborting v7 cuda23 tasks on your GTX 295 host, not your GTX580 hosts, and if you were then there would be a scheduler Bug because the Cuda23 Can't be run on Fermi's and Keplers.

Claggy

Richard, Claggy

AP:
I only run AP on the i7 with the CPU. I don't run AP on the GPUs in this box and I don't run AP on any of the other boxes (CPU or GPU).

MB:
v7 cuda50 was taking circa 80 minutes to run on the 295s. Far to long, so any cuda50 WUs landing here get aborted.

v7 cuda50 wus landing on any of the 580s also get aborted. The ones that have landed here and I have seen seem to have an exponential processing time albiet not as bad as the 295s. I must say that since implementing this practice the number of cuda50 WUs landing on these GPUs is declining to almost being non existent.

v7 cuda23 wus landed on the Q6600 with dual GTX580s. These appeared to be going down the same path as the cuda50 so they were aborted.

The 295s are now running cuda32 and cuda42 WUs for the GPU.
One of the 580s is running only cuda42 WUs at present, the other is running cuda32 and cuda42 WUs at present (just burnt another cuda50 WU there).

Let the different Cuda version tasks complete, the progress indication on v7 isn't Linear, there is speedup over the second half, let the different Cuda versions tasks complete, then the scheduler will pick the fastest version, at the moment you're prolonging it,

Claggy

Isn't is possible to download stock v7 CPU app and put it in app_info.xml ?

sure it's possible.
We just hope to provide faster app at Monday.
For now stock v7 CPU could go.

What's the URL for stock app then? (until monday)

You would need, as a minimum,

http://boinc2.ssl.berkeley.edu/sah/download_fanout/setiathome_7.00_windows_intelx86.exe
http://boinc2.ssl.berkeley.edu/sah/download_fanout/libfftw3f-3-3_upx.dll

I've deliberately not made them clickable, because I want casual readers to stop and think before downloading.

The file sizes are 484,352 and 1,049,920 bytes respectively. Internet Explorer seems to have a habit of truncating manual downloads: Chrome seems better.

Thanks works fine it seems. DL with Chrome with no probs.

Could you, or someone other post the app_info.xml file entries part for stock SAHv7 CPU app?

Thanks.


* Best regards! :-) * Philip J. Fry, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. *

---