[In a more serious answer to the question of working on the bigger issues] Since there is so much more to do, this year I'll try find if there is a way I can dedicate more time to SaH and other general tool development [Will involve taking less contract work, and still finding some means to feed myself and dog]. If I find a way, I'll let the other devs know how I went about it.

---

Chaos: When the present determines the future, but the approximate present does not approximately determine the future.
Edward Lorenz

Has this been covered?

running MB V8's (just as on MB V7's) when the progress hits 82% the WU runs much faster ... (This was covered a long time ago ... I believe. But on my GPU ...

running opencl_nvidia_sah ...

00-40% requires 4.5 sec/% progress
40-60% requires 3 sec/% progress
70%- requires 1 sec/% progress

I.E. the speed increases starting sooner and grows ... Is this expected behavior??

Ed F

---

I.E. the speed increases starting sooner and grows ... Is this expected behavior??

Ed F

Yeah processing changes its mix of searches depending on angle range of the task [, which chirp rate the app is up to], and each of the processing stages likely has different efficiency.

---

Chaos: When the present determines the future, but the approximate present does not approximately determine the future.
Edward Lorenz

Final count for CUDA v8.00 apps:

SETI@home v8 8.00 windows_intelx86 (cuda23)
Number of tasks completed 540
Max tasks per day 612
Number of tasks today 0
Consecutive valid tasks 579
Average processing rate 135.22 GFLOPS
Average turnaround time 0.27 days
SETI@home v8 8.00 windows_intelx86 (cuda32)
Number of tasks completed 118
Max tasks per day 152
Number of tasks today 0
Consecutive valid tasks 119
Average processing rate 92.41 GFLOPS
Average turnaround time 0.56 days
SETI@home v8 8.00 windows_intelx86 (cuda42)
Number of tasks completed 47
Max tasks per day 83
Number of tasks today 0
Consecutive valid tasks 50
Average processing rate 73.79 GFLOPS
Average turnaround time 0.60 days
SETI@home v8 8.00 windows_intelx86 (cuda50)
Number of tasks completed 61
Max tasks per day 96
Number of tasks today 0
Consecutive valid tasks 63
Average processing rate 84.84 GFLOPS
Average turnaround time 0.60 days

BOINC choice coincide with offline benchmarking this time. Will see what 8.01 gives.

---

News about SETI opt app releases: https://twitter.com/Raistmer

All right, I haven't changed anything since I got the app_config working yesterday. When last we left my adventures, I was running two Beta tasks, each using 0.5 GPU.

Right now, Boinc says it's running one Einstein using 0.5 GPU, and one Beta using 1.0 GPU. Total of 1.5 GPU. (Did I mention I only have one GPU in there?)

W. T. F. ? ? ?

(This is on the i7 with the 440. Beta host 66539.)

---

David
signature sent back to alpha testing

I think that like CPUs, BOINC truncates the number in use. So 1.5==1, 1.9999==1, 2.0==2.

---

I think that like CPUs, BOINC truncates the number in use. So 1.5==1, 1.9999==1, 2.0==2.

And like files ;)

---

Chaos: When the present determines the future, but the approximate present does not approximately determine the future.
Edward Lorenz

Upload issue

1/22/2016 9:52:32 PM | SETI@home Beta Test | Started upload of 06ap11ag.21334.4157.8.42.253_1_0
1/22/2016 9:52:34 PM | SETI@home Beta Test | [error] Error reported by file upload server: can't open file
1/22/2016 9:52:34 PM | SETI@home Beta Test | Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient upload error

---

Upload issue

1/22/2016 9:52:32 PM | SETI@home Beta Test | Started upload of 06ap11ag.21334.4157.8.42.253_1_0
1/22/2016 9:52:34 PM | SETI@home Beta Test | [error] Error reported by file upload server: can't open file
1/22/2016 9:52:34 PM | SETI@home Beta Test | Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient upload error

Had one of those a couple days ago. Finally had to nuke the job, as it became clear that https://setiweb.ssl.berkeley.edu/beta/result.php?resultid=22046064 would never upload.

---

If I can help out by testing something, please let me know.
Available hardware and software is listed in my profile here.

Upload issue

1/22/2016 9:52:32 PM | SETI@home Beta Test | Started upload of 06ap11ag.21334.4157.8.42.253_1_0
1/22/2016 9:52:34 PM | SETI@home Beta Test | [error] Error reported by file upload server: can't open file
1/22/2016 9:52:34 PM | SETI@home Beta Test | Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient upload error

It's a long time since I saw one of those (years, I think), but I think it's a two-part error message.

Error reported by file upload server:

OK, what was it?

can't open file

And that second part actually comes from the local client: it's reported to the upload server, and the upload server reports it back down again.

If it's a persistent error for a single task, look in the project directory to see if the file (the one ending in _1_0) is actually there - I think the cases I've seen have been when the uploadable file has been deleted prematurely.

Then, you could search back through stdoutdae.txt for the main filename (06ap11ag.21334.4157.8.42.253) to work out the whole life-cycle of that workunit. I think the chances are that you will find a successful upload in there somewhere, but for some reason BOINC (the local client) didn't update the task status properly. Maybe David (Anderson) could comment on that:

findstr 06ap11ag.21334.4157.8.42.253 stdoutdae.txt

would give him something to work on, since it's on one of your Windows machines.

With extreme care, it is possible to edit client_state.xml to indicate that the upload has completed successfully, but it's simpler to just abort it and let somebody else have a go.

All right, I haven't changed anything since I got the app_config working yesterday. When last we left my adventures, I was running two Beta tasks, each using 0.5 GPU.

Right now, Boinc says it's running one Einstein using 0.5 GPU, and one Beta using 1.0 GPU. Total of 1.5 GPU. (Did I mention I only have one GPU in there?)

Usually, that means that it's working on a Beta task which was downloaded before you put the app_config file into place, while you were still running tasks one at a time.

When you 'read config files', the new setting goes into effect immediately, but the BOINC Manager display isn't updated for tasks already cached. It's only newly downloaded tasks (after app_config came into effect) which are correctly marked with '0.5 GPU' or whatever.

That's another one for David Anderson.

All right, I haven't changed anything since I got the app_config working yesterday. When last we left my adventures, I was running two Beta tasks, each using 0.5 GPU.

Right now, Boinc says it's running one Einstein using 0.5 GPU, and one Beta using 1.0 GPU. Total of 1.5 GPU. (Did I mention I only have one GPU in there?)

Usually, that means that it's working on a Beta task which was downloaded before you put the app_config file into place, while you were still running tasks one at a time.

When you 'read config files', the new setting goes into effect immediately, but the BOINC Manager display isn't updated for tasks already cached. It's only newly downloaded tasks (after app_config came into effect) which are correctly marked with '0.5 GPU' or whatever.

That's another one for David Anderson.

Okay, that makes sense.

---

David
signature sent back to alpha testing

Upload issue

1/22/2016 9:52:32 PM | SETI@home Beta Test | Started upload of 06ap11ag.21334.4157.8.42.253_1_0
1/22/2016 9:52:34 PM | SETI@home Beta Test | [error] Error reported by file upload server: can't open file
1/22/2016 9:52:34 PM | SETI@home Beta Test | Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient upload error

It's a long time since I saw one of those (years, I think), but I think it's a two-part error message.

Error reported by file upload server:

OK, what was it?

can't open file

And that second part actually comes from the local client: it's reported to the upload server, and the upload server reports it back down again.

If it's a persistent error for a single task, look in the project directory to see if the file (the one ending in _1_0) is actually there - I think the cases I've seen have been when the uploadable file has been deleted prematurely.

File is present.

Then, you could search back through stdoutdae.txt for the main filename (06ap11ag.21334.4157.8.42.253) to work out the whole life-cycle of that workunit. I think the chances are that you will find a successful upload in there somewhere, but for some reason BOINC (the local client) didn't update the task status properly. Maybe David (Anderson) could comment on that:

findstr 06ap11ag.21334.4157.8.42.253 stdoutdae.txt

would give him something to work on, since it's on one of your Windows machines.

20-Jan-2016 16:57:35 [SETI@home Beta Test] Starting task 06ap11ag.21334.4157.8.42.253_1
20-Jan-2016 16:58:02 [SETI@home Beta Test] Computation for task 06ap11ag.21334.4157.8.42.253_1 finished
20-Jan-2016 17:13:07 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 17:15:08 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 17:15:08 [SETI@home Beta Test] Backing off 00:01:57 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 17:23:19 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 17:25:20 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 17:25:20 [SETI@home Beta Test] Backing off 00:01:24 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 17:47:43 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 17:49:43 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 17:49:43 [SETI@home Beta Test] Backing off 00:01:15 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 17:59:32 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 18:01:33 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 18:01:33 [SETI@home Beta Test] Backing off 00:01:03 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 18:17:40 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 18:19:41 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 18:19:41 [SETI@home Beta Test] Backing off 00:01:53 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 18:24:02 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 18:26:03 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 18:26:03 [SETI@home Beta Test] Backing off 00:01:48 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 18:58:25 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 19:00:27 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 19:00:27 [SETI@home Beta Test] Backing off 00:01:44 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 19:16:36 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 19:18:37 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 19:18:37 [SETI@home Beta Test] Backing off 00:01:55 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 19:54:44 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 19:56:45 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 19:56:45 [SETI@home Beta Test] Backing off 00:01:18 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 19:58:46 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 20:00:47 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 20:00:47 [SETI@home Beta Test] Backing off 00:01:03 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 20:08:59 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 20:11:01 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 20:11:01 [SETI@home Beta Test] Backing off 00:01:26 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 20:17:02 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 20:19:03 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 20:19:03 [SETI@home Beta Test] Backing off 00:01:18 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 20:43:26 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 20:45:27 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 20:45:27 [SETI@home Beta Test] Backing off 00:01:13 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 21:03:31 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 21:05:32 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 21:05:32 [SETI@home Beta Test] Backing off 00:01:54 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 21:28:01 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 21:30:02 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 21:30:02 [SETI@home Beta Test] Backing off 00:01:09 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 21:38:04 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 21:40:05 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient HTTP error
20-Jan-2016 21:40:05 [SETI@home Beta Test] Backing off 00:01:43 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 22:31:00 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0

Note there is no message here about the result of the upload!

20-Jan-2016 22:31:47 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 22:31:48 [SETI@home Beta Test] Error reported by file upload server: can't open file
20-Jan-2016 22:31:48 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient upload error
20-Jan-2016 22:31:48 [SETI@home Beta Test] Backing off 00:02:28 on upload of 06ap11ag.21334.4157.8.42.253_1_0

Many more of the same block follow.

Looking at the entire log this may explain what happened:

20-Jan-2016 22:31:00 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 22:31:01 [SETI@home Beta Test] Finished upload of 06ap11ag.21334.4157.8.42.251_1_0
20-Jan-2016 22:31:01 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4566.8.42.68_0_0
20-Jan-2016 22:31:03 [SETI@home] Finished download of 16ap11ab.32302.7429.14.41.178
20-Jan-2016 22:31:03 [SETI@home] Started download of 18ap11ag.1711.6202.5.32.216
20-Jan-2016 22:31:04 [SETI@home] Finished download of 16ap11ab.32302.7429.14.41.184
20-Jan-2016 22:31:04 [SETI@home] Finished download of 18ap11ag.1711.6202.5.32.168
20-Jan-2016 22:31:04 [SETI@home] Finished download of 18ap11ag.1711.6202.5.32.213
20-Jan-2016 22:31:04 [SETI@home] Started download of 18ap11ag.1711.6202.5.32.71
20-Jan-2016 22:31:04 [SETI@home] Started download of 16ap11ab.20138.10292.13.40.225
20-Jan-2016 22:31:04 [SETI@home] Started download of 18ap11ag.1711.6202.5.32.220
20-Jan-2016 22:31:07 [SETI@home Beta Test] Finished upload of 06ap11ag.21334.4566.8.42.94_1_0
20-Jan-2016 22:31:07 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.221_1_0
20-Jan-2016 22:31:15 [SETI@home Beta Test] Finished upload of 06ap11ag.21334.4566.8.42.1_1_0
20-Jan-2016 22:31:15 [SETI@home Beta Test] Finished upload of 06ap11ag.21334.4566.8.42.68_0_0
20-Jan-2016 22:31:15 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.222_0_0
20-Jan-2016 22:31:15 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.244_1_0
20-Jan-2016 22:31:16 [---] Suspending computation - an exclusive app is running
20-Jan-2016 22:31:16 [---] Suspending network activity - an exclusive app is running
20-Jan-2016 22:31:47 [---] Resuming computation
20-Jan-2016 22:31:47 [---] Resuming network activity
20-Jan-2016 22:31:47 [ATLAS@home] Started upload of jU5LDmYXbfnnDDn7oo6G73TpABFKDmABFKDm0yGKDmABFKDmUn1Gvn_0_ATLAS_result
20-Jan-2016 22:31:47 [ATLAS@home] Started upload of Nv4KDm6SbfnnDDn7oo6G73TpABFKDmABFKDmZzMKDmABFKDm26azbm_0_ATLAS_result
20-Jan-2016 22:31:47 [ATLAS@home] Started upload of m8ZLDmziXfnnDDn7oo6G73TpABFKDmABFKDmF7JKDmABFKDmoTRPVm_1_ATLAS_result
20-Jan-2016 22:31:47 [ATLAS@home] Started upload of tCYLDmjUbfnnDDn7oo6G73TpABFKDmABFKDm2KFKDmABFKDmo52IQm_0_ATLAS_result
20-Jan-2016 22:31:47 [pogs] Started upload of MaNGA_8601-6104_area26440158_1_0
20-Jan-2016 22:31:47 [pogs] Started upload of MaNGA_8601-6104_area26440131_0_0
20-Jan-2016 22:31:47 [pogs] Started upload of MaNGA_8601-6104_area26440128_0_0
20-Jan-2016 22:31:47 [pogs] Started upload of MaNGA_8601-6104_area26440152_0_0
20-Jan-2016 22:31:47 [rosetta@home] Started upload of rb_01_17_62187_106509__t000__1_C1_SAVE_ALL_OUT_IGNORE_THE_REST_324775_878_0_0
20-Jan-2016 22:31:47 [rosetta@home] Started upload of rb_01_18_61979_106518__t000__1_C1_SAVE_ALL_OUT_IGNORE_THE_REST_324792_155_0_0
20-Jan-2016 22:31:47 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 22:31:47 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.221_1_0
20-Jan-2016 22:31:47 [SETI@home] Started download of 18ap11ag.1711.6202.5.32.216
20-Jan-2016 22:31:47 [SETI@home] Started download of 18ap11ag.1711.6202.5.32.71
20-Jan-2016 22:31:47 [SETI@home] Started download of 16ap11ab.20138.10292.13.40.225
20-Jan-2016 22:31:47 [SETI@home] Started download of 18ap11ag.1711.6202.5.32.220
20-Jan-2016 22:31:47 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.222_0_0
20-Jan-2016 22:31:47 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4157.8.42.244_1_0
20-Jan-2016 22:31:48 [SETI@home Beta Test] Error reported by file upload server: can't open file
20-Jan-2016 22:31:48 [SETI@home Beta Test] Temporarily failed upload of 06ap11ag.21334.4157.8.42.253_1_0: transient upload error
20-Jan-2016 22:31:48 [SETI@home Beta Test] Backing off 00:02:28 on upload of 06ap11ag.21334.4157.8.42.253_1_0
20-Jan-2016 22:31:48 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4566.8.42.56_2_0
20-Jan-2016 22:31:50 [SETI@home] Finished download of 18ap11ag.1711.6202.5.32.216
20-Jan-2016 22:31:50 [SETI@home] Started download of 18ap11ag.1711.6202.5.32.223
20-Jan-2016 22:31:51 [SETI@home] Finished download of 16ap11ab.20138.10292.13.40.225
20-Jan-2016 22:31:51 [SETI@home] Finished download of 18ap11ag.1711.6202.5.32.220
20-Jan-2016 22:31:51 [SETI@home] Started download of 18ap11ag.1711.6202.5.32.113
20-Jan-2016 22:31:51 [SETI@home] Started download of 18ap11ag.1711.6202.5.32.226
20-Jan-2016 22:31:53 [SETI@home] Finished download of 18ap11ag.1711.6202.5.32.71
20-Jan-2016 22:31:53 [SETI@home] Started download of 16ap11ab.32302.7429.14.41.21
20-Jan-2016 22:32:02 [SETI@home Beta Test] Finished upload of 06ap11ag.21334.4157.8.42.222_0_0
20-Jan-2016 22:32:02 [SETI@home Beta Test] Finished upload of 06ap11ag.21334.4157.8.42.244_1_0
20-Jan-2016 22:32:02 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4566.8.42.87_1_0
20-Jan-2016 22:32:02 [SETI@home Beta Test] Started upload of 06ap11ag.21334.4566.8.42.57_0_0
20-Jan-2016 22:32:05 [SETI@home Beta Test] Finished upload of 06ap11ag.21334.4157.8.42.221_1_0

I suspect that network activity got suspended while the app was waiting for a reply that the file transfer was complete. For some reason the client isn't being told that the file has been received and to delete it.

I'll end up aborting it.

---

Well, I have moved over to main now, after having ripped out of the new installer what I needed. (thanks Richard, and all others who have been involved in that).

I never use the installer as an installer, I just rip out what I need from it with 7-zip, and remove from the .aistubs sections not needed.

I take it that now that v8 has been released to main, there's no need for me to continue testing v8's here on beta?

It was fun. Thanks for the coffee...:-)

I asked before, but I don't think anyone answered (if they did, it went over my head). (Or maybe I asked in a different thread and don't remember which one.)

Here is my app info for my gt 630.

SETI@home v8 8.01 windows_intelx86 (cuda32)
Number of tasks completed	29
Max tasks per day	70
Number of tasks today	0
Consecutive valid tasks	37
Average processing rate	18.17 GFLOPS
Average turnaround time	0.60 days
SETI@home v8 8.01 windows_intelx86 (cuda42)
Number of tasks completed	28
Max tasks per day	69
Number of tasks today	0
Consecutive valid tasks	36
Average processing rate	17.59 GFLOPS
Average turnaround time	0.44 days
SETI@home v8 8.01 windows_intelx86 (cuda50)
Number of tasks completed	17
Max tasks per day	50
Number of tasks today	0
Consecutive valid tasks	17
Average processing rate	17.10 GFLOPS
Average turnaround time	0.68 days

My goal for this machine is minimal impact on the CPU. When I install the new Lunatics for Main on it, do I want to go with 43, 42, or 50? 32 has the highest APR. 42 has the middle APR and shortest turnaround time.

---------------------

And here is the app info for my gt 440.

SETI@home v8 8.00 windows_intelx86 (cuda50)
Number of tasks completed	72
Max tasks per day	110
Number of tasks today	0
Consecutive valid tasks	77
Average processing rate	56.43 GFLOPS
Average turnaround time	0.45 days
SETI@home v8 8.06 windows_intelx86 (opencl_nvidia_sah)
Number of tasks completed	248
Max tasks per day	300
Number of tasks today	0
Consecutive valid tasks	267
Average processing rate	66.26 GFLOPS
Average turnaround time	0.63 days
SETI@home v8 8.01 windows_intelx86 (cuda32)
Number of tasks completed	10
Max tasks per day	45
Number of tasks today	0
Consecutive valid tasks	12
Average processing rate	25.64 GFLOPS
Average turnaround time	0.20 days
SETI@home v8 8.01 windows_intelx86 (cuda42)
Number of tasks completed	5
Max tasks per day	40
Number of tasks today	0
Consecutive valid tasks	7
Average processing rate	15.31 GFLOPS
Average turnaround time	1.38 days

I included the v8.00 cuda50s here because it hasn't done any 8.01 50s. In this case, there is also opencl to consider. My goal for this box is maximum production.

I realize the sample sizes are smaller here, but what I see is cuda42 having a MUCH lower APR than 32 and almost 6x the turnaround time. OTOH, boinc seems to have settled on 42 as the best; it just downloaded a whole bunch of new 42s. Maybe I'll wait for some of those to get done and see what the effect is on the stats.

Does a high APR mean you're getting the most work done, or a low one?

---

David
signature sent back to alpha testing

High APR is good, and I'd usually choose that above turnround time. But cuda42 also sounds good.

Did we establish which version of the GT 630 you have?

You can run the lunatics installer and take a look at the NVIDEO screen, it gives some info on 32 recommended for this, 42 for this.

You should be able to exit the installer without any changes at that point.

for CPU, make note of your BOINC startup message about CPU details, your i7 is likely best on AVX, other computer might be an SSE.

High APR is good, and I'd usually choose that above turnround time. But cuda42 also sounds good.

Did we establish which version of the GT 630 you have?

Thanks for reminding me. I just now downloaded and installed GPU-Z.

My 630 is a GF108 with DDR3 memory.

[edit]
Brent, I'm not crunching with the CPU on the Pentium 4, so that's moot.

---

David
signature sent back to alpha testing

I think we'd probably recommend cuda42 for a 'GF' for Fermi.

I think we'd probably recommend cuda42 for a 'GF' for Fermi.

Okay, thanks. I'll go with that then.

---

David
signature sent back to alpha testing