gpu tasks - don't got any

Message boards : Number crunching : gpu tasks - don't got any
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Profile Mike Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 34253
Credit: 79,922,639
RAC: 80
Germany
Message 1590699 - Posted: 23 Oct 2014, 13:45:56 UTC - in response to Message 1590695.  
Last modified: 23 Oct 2014, 13:50:55 UTC

Another 30 Pulses. Doesn't look good.
What are your suggestions for repeated 30 Pulses?

Shouldn't the App Rename the New Bin files to the New Driver?


No, only new app version is generating new binaries.

He has one normal unit also so i would just wait and see if one got invalid.


With each crime and every kindness we birth our future.
ID: 1590699 · Report as offensive
merle van osdol

Send message
Joined: 23 Oct 02
Posts: 809
Credit: 1,980,117
RAC: 0
United States
Message 1590704 - Posted: 23 Oct 2014, 13:57:36 UTC

After the deletion of the bin files and the update to 14.9 my wu is stalled out at 90%.
merle - vote yes for freedom of speech
ID: 1590704 · Report as offensive
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1590708 - Posted: 23 Oct 2014, 14:04:57 UTC - in response to Message 1590699.  

Shouldn't the App Rename the New Bin files to the New Driver?

No, only new app version is generating new binaries.

Seems the 'new' apps (don't know since which version) makes new .bin for different driver:

My files:
AstroPulse_Kernels_r2690.cl_Turks.bin_V7_TWIN_FFA_CAL141646
AP_clFFTplan_Turks_32768_gr64_lr8_wg256_tw0_r2690.bin_CAL141646


But maybe if CAL version do not change (or not exist?) in new drivers this versioning do not happen - i.e. always CAL141848
 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1590708 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1590710 - Posted: 23 Oct 2014, 14:08:10 UTC - in response to Message 1590704.  

After the deletion of the bin files and the update to 14.9 my wu is stalled out at 90%.

Try rebooting the machine again. Then look in the Slot folder and look for errors at the bottom of the stderr.txt file for that task.
ID: 1590710 · Report as offensive
merle van osdol

Send message
Joined: 23 Oct 02
Posts: 809
Credit: 1,980,117
RAC: 0
United States
Message 1590763 - Posted: 23 Oct 2014, 15:41:00 UTC - in response to Message 1590710.  

How do you find a particular task in the slots file. You have to go thru looking in each slot to fine it?

After the deletion of the bin files and the update to 14.9 my wu is stalled out at 90%.

Try rebooting the machine again. Then look in the Slot folder and look for errors at the bottom of the stderr.txt file for that task.

merle - vote yes for freedom of speech
ID: 1590763 · Report as offensive
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1590773 - Posted: 23 Oct 2014, 15:55:59 UTC - in response to Message 1590763.  
Last modified: 23 Oct 2014, 16:02:48 UTC

How do you find a particular task in the slots file. You have to go thru looking in each slot to fine it?

In BOINC Manager select the task
- click button [Properties] at left
- almost at bottom look for 'slots/X'

Or in BoincTasks for the same info - Right-Click the task -> Properties
 
 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1590773 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14649
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1590776 - Posted: 23 Oct 2014, 15:56:18 UTC - in response to Message 1590763.  

How do you find a particular task in the slots file. You have to go thru looking in each slot to fine it?

Highlight the task in the task list and click the 'Properties' command button.
ID: 1590776 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1590781 - Posted: 23 Oct 2014, 16:02:06 UTC - in response to Message 1590763.  

I see you are still suffering the 30 Pulse Plague and now Driver Restarts? I would try stopping everything, reinstalling the Driver, and Rebooting the Computer. If you still have the same problems after that try removing the -oclFFT_plan 256 16 256 entry and see if that helps.
ID: 1590781 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1590989 - Posted: 23 Oct 2014, 21:47:25 UTC

LOL
23/10/2014 23:12:12 | SETI@home | Not requesting tasks: don't need (CPU: blocked by project preferences; AMD/ATI GPU: job cache full)

My BOINC has one AP v7 in cache, that's all it has in cache. It's estimated to run for 12 hours 17 minutes, so theoretically yes according to BOINC that's enough work for the 1 day + 0.05 days work preference plus % of time BOINC is running 18.96% plus While BOINC running, % of time GPU work is allowed 63.61%.

Trouble is, these APs run for 1,800 seconds and then finish. I only have had 5 of these new AP v7s so far. Still another --what's the amount the server needs these days, 11? so 6 then?-- to go before we're hopefully rid of this empty cache circumstance. Of course now there's no APs to be had.
ID: 1590989 · Report as offensive
Profile Mike Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 34253
Credit: 79,922,639
RAC: 80
Germany
Message 1590993 - Posted: 23 Oct 2014, 21:52:56 UTC - in response to Message 1590989.  

LOL
23/10/2014 23:12:12 | SETI@home | Not requesting tasks: don't need (CPU: blocked by project preferences; AMD/ATI GPU: job cache full)

My BOINC has one AP v7 in cache, that's all it has in cache. It's estimated to run for 12 hours 17 minutes, so theoretically yes according to BOINC that's enough work for the 1 day + 0.05 days work preference plus % of time BOINC is running 18.96% plus While BOINC running, % of time GPU work is allowed 63.61%.

Trouble is, these APs run for 1,800 seconds and then finish. I only have had 5 of these new AP v7s so far. Still another --what's the amount the server needs these days, 11? so 6 then?-- to go before we're hopefully rid of this empty cache circumstance. Of course now there's no APs to be had.


Yes, you need 11 non outlier tasks which means less than 10% blanking and non overflows.


With each crime and every kindness we birth our future.
ID: 1590993 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1590996 - Posted: 23 Oct 2014, 21:57:09 UTC - in response to Message 1590993.  

Got a full cache again of v7 MB and one AP 7... so in 12 x 15 minutes, it's back to not asking for work due to the AP v7 in the way. Dumb looking yoyo effect. ;-)

So the server status page doesn't show the new AP v7s in the 'ready to send' queue then?
ID: 1590996 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14649
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1591035 - Posted: 23 Oct 2014, 23:18:23 UTC - in response to Message 1590996.  

Got a full cache again of v7 MB and one AP 7... so in 12 x 15 minutes, it's back to not asking for work due to the AP v7 in the way. Dumb looking yoyo effect. ;-)

So the server status page doesn't show the new AP v7s in the 'ready to send' queue then?

Didn't you know - the whole of BOINC and SETI is psychological gameplay, designed by the white mice as an experiment on the human race?

Parts of the gameplay include illogical hazards and undocumented resources.
ID: 1591035 · Report as offensive
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1591469 - Posted: 24 Oct 2014, 17:57:36 UTC - in response to Message 1591035.  

;) And when we will be near of fixing all the glitches and the experiment is almost over - beware, Vogons are coming ...
 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1591469 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1591475 - Posted: 24 Oct 2014, 18:15:51 UTC - in response to Message 1591469.  
Last modified: 24 Oct 2014, 18:30:40 UTC

Apparently his CPU was running really Hot. That could explain all the problems. It will be interesting to see how it works with the heat problem resolved.

He could have all those CPU tasks sent back as ATI tasks if he wanted. All he would have to do is Set the Preferences to only ATI AP7s (UnCheck Use CPU), Hit the BOINC Manager Update button a couple times to make sure it sees the change, then Hit the 'Reset project' button.

Of course he would lose all the in progress CPU tasks, but gain around 90 ATI tasks.


Are those New APs showing on the SSP? http://setiathome.berkeley.edu/sah_status.html
??
ID: 1591475 · Report as offensive
Josef W. Segur
Volunteer developer
Volunteer tester

Send message
Joined: 30 Oct 99
Posts: 4504
Credit: 1,414,761
RAC: 0
United States
Message 1591564 - Posted: 24 Oct 2014, 21:44:14 UTC - in response to Message 1591475.  

...
Are those New APs showing on the SSP? http://setiathome.berkeley.edu/sah_status.html
??

The "Data Distribution State" is still showing AP v6 numbers. The "Server status" and "Splitter status" sections do show AP v7 activity.
                                                                   Joe
ID: 1591564 · Report as offensive
mrchips
Avatar

Send message
Joined: 12 Dec 04
Posts: 17
Credit: 26,590,842
RAC: 8
United States
Message 1600401 - Posted: 12 Nov 2014, 22:12:19 UTC

Have not gotten any seti GPU tasks for weeks, can anyone tell me why?
I have not changed any of my settings.
Running NVidia.
ID: 1600401 · Report as offensive
Profile Wiggo
Avatar

Send message
Joined: 24 Jan 00
Posts: 34744
Credit: 261,360,520
RAC: 489
Australia
Message 1600418 - Posted: 12 Nov 2014, 23:21:15 UTC - in response to Message 1600401.  

Have not gotten any seti GPU tasks for weeks, can anyone tell me why?
I have not changed any of my settings.
Running NVidia.

Downgrade your video driver to 337.88 (or earlier) as the latest drivers do not support your older hardware correctly, @Pre-FERMI nVidia GPU users: Important warning. ;-)

Cheers.
ID: 1600418 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1600423 - Posted: 12 Nov 2014, 23:41:58 UTC - in response to Message 1600418.  
Last modified: 13 Nov 2014, 0:29:12 UTC

Have not gotten any seti GPU tasks for weeks, can anyone tell me why?
I have not changed any of my settings.
Running NVidia.

Downgrade your video driver to 337.88 (or earlier) as the latest drivers do not support your older hardware correctly, @Pre-FERMI nVidia GPU users: Important warning. ;-)

Cheers.

But that is only for the NV OpenCL Astropulse v6 and v7 apps,

the Cuda22, Cuda23, Cuda32, Cuda42 and Cuda50 apps work correctly on 340.52 drivers, I've done Benches to prove that,
So the scheduler should still send Seti v7 work to pre-Fermi's with 340.52 drivers, It was (via anonymous platform) to my E8500/9800GTX+ host:

setiathome_7.00_windows_intelx86.exe -verb / PG0009_v7.wu :
Result cached, skipping execution
507.876 secs Elapsed
500.560 secs CPU time

Stderr.txt : not found
------------
Lunatics_x41zc_win32_cuda23.exe / PG0009_v7.wu :
AppName: Lunatics_x41zc_win32_cuda23.exe
AppArgs:
TaskName: PG0009_v7.wu
Started at : 19:05:44.470
Ended at : 19:12:17.304
390.907 secs Elapsed
12.995 secs CPU time
Speedup : 97.40%
Ratio : 38.52x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

------------
Lunatics_x41zc_win32_cuda32.exe / PG0009_v7.wu :
AppName: Lunatics_x41zc_win32_cuda32.exe
AppArgs:
TaskName: PG0009_v7.wu
Started at : 19:12:21.826
Ended at : 19:19:02.753
400.818 secs Elapsed
15.616 secs CPU time
Speedup : 96.88%
Ratio : 32.05x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

------------
Lunatics_x41zc_win32_cuda42.exe / PG0009_v7.wu :
AppName: Lunatics_x41zc_win32_cuda42.exe
AppArgs:
TaskName: PG0009_v7.wu
Started at : 19:19:06.045
Ended at : 19:25:47.474
401.351 secs Elapsed
13.151 secs CPU time
Speedup : 97.37%
Ratio : 38.06x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

------------
Lunatics_x41zc_win32_cuda50.exe / PG0009_v7.wu :
AppName: Lunatics_x41zc_win32_cuda50.exe
AppArgs:
TaskName: PG0009_v7.wu
Started at : 19:25:50.764
Ended at : 19:33:05.918
435.054 secs Elapsed
12.262 secs CPU time
Speedup : 97.55%
Ratio : 40.82x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.99%

------------
Lunatics_x41zc_win32_cuda60.exe / PG0009_v7.wu :
AppName: Lunatics_x41zc_win32_cuda60.exe
AppArgs:
TaskName: PG0009_v7.wu
Started at : 19:33:09.225
Ended at : 19:40:58.640
469.311 secs Elapsed
12.511 secs CPU time
Speedup : 97.50%
Ratio : 40.01x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.53%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.53%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.53%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.53%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0009_v7.wu.res
Result : Strongly similar, Q= 99.54%

------------
setiathome_7.00_windows_intelx86.exe -verb / PG0395_v7.wu :
Result cached, skipping execution
542.633 secs Elapsed
538.547 secs CPU time

Stderr.txt : not found
------------
Lunatics_x41zc_win32_cuda23.exe / PG0395_v7.wu :
AppName: Lunatics_x41zc_win32_cuda23.exe
AppArgs:
TaskName: PG0395_v7.wu
Started at : 19:41:02.111
Ended at : 19:42:46.179
104.017 secs Elapsed
13.884 secs CPU time
Speedup : 97.42%
Ratio : 38.79x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

------------
Lunatics_x41zc_win32_cuda32.exe / PG0395_v7.wu :
AppName: Lunatics_x41zc_win32_cuda32.exe
AppArgs:
TaskName: PG0395_v7.wu
Started at : 19:42:49.589
Ended at : 19:44:51.832
122.191 secs Elapsed
15.694 secs CPU time
Speedup : 97.09%
Ratio : 34.32x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

------------
Lunatics_x41zc_win32_cuda42.exe / PG0395_v7.wu :
AppName: Lunatics_x41zc_win32_cuda42.exe
AppArgs:
TaskName: PG0395_v7.wu
Started at : 19:44:55.135
Ended at : 19:47:04.853
129.663 secs Elapsed
12.667 secs CPU time
Speedup : 97.65%
Ratio : 42.52x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

------------
Lunatics_x41zc_win32_cuda50.exe / PG0395_v7.wu :
AppName: Lunatics_x41zc_win32_cuda50.exe
AppArgs:
TaskName: PG0395_v7.wu
Started at : 19:47:08.157
Ended at : 19:49:52.243
164.030 secs Elapsed
12.324 secs CPU time
Speedup : 97.71%
Ratio : 43.70x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.94%

------------
Lunatics_x41zc_win32_cuda60.exe / PG0395_v7.wu :
AppName: Lunatics_x41zc_win32_cuda60.exe
AppArgs:
TaskName: PG0395_v7.wu
Started at : 19:49:55.555
Ended at : 19:53:16.815
201.198 secs Elapsed
12.745 secs CPU time
Speedup : 97.63%
Ratio : 42.26x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.88%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.93%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.93%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.93%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0395_v7.wu.res
Result : Strongly similar, Q= 99.93%

------------
setiathome_7.00_windows_intelx86.exe -verb / PG0444_v7.wu :
Result cached, skipping execution
475.018 secs Elapsed
471.669 secs CPU time

Stderr.txt : not found
------------
Lunatics_x41zc_win32_cuda23.exe / PG0444_v7.wu :
AppName: Lunatics_x41zc_win32_cuda23.exe
AppArgs:
TaskName: PG0444_v7.wu
Started at : 19:53:20.218
Ended at : 19:54:56.093
95.825 secs Elapsed
13.946 secs CPU time
Speedup : 97.04%
Ratio : 33.82x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

------------
Lunatics_x41zc_win32_cuda32.exe / PG0444_v7.wu :
AppName: Lunatics_x41zc_win32_cuda32.exe
AppArgs:
TaskName: PG0444_v7.wu
Started at : 19:54:59.482
Ended at : 19:56:52.913
113.383 secs Elapsed
14.789 secs CPU time
Speedup : 96.86%
Ratio : 31.89x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

------------
Lunatics_x41zc_win32_cuda42.exe / PG0444_v7.wu :
AppName: Lunatics_x41zc_win32_cuda42.exe
AppArgs:
TaskName: PG0444_v7.wu
Started at : 19:56:56.216
Ended at : 19:58:57.261
120.989 secs Elapsed
12.714 secs CPU time
Speedup : 97.30%
Ratio : 37.10x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

------------
Lunatics_x41zc_win32_cuda50.exe / PG0444_v7.wu :
AppName: Lunatics_x41zc_win32_cuda50.exe
AppArgs:
TaskName: PG0444_v7.wu
Started at : 19:59:00.587
Ended at : 20:01:35.861
155.220 secs Elapsed
12.090 secs CPU time
Speedup : 97.44%
Ratio : 39.01x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.97%

------------
Lunatics_x41zc_win32_cuda60.exe / PG0444_v7.wu :
AppName: Lunatics_x41zc_win32_cuda60.exe
AppArgs:
TaskName: PG0444_v7.wu
Started at : 20:01:39.160
Ended at : 20:04:51.774
192.558 secs Elapsed
11.950 secs CPU time
Speedup : 97.47%
Ratio : 39.47x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.78%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.78%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.78%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.78%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG0444_v7.wu.res
Result : Strongly similar, Q= 99.78%

------------
setiathome_7.00_windows_intelx86.exe -verb / PG1327_v7.wu :
Result cached, skipping execution
386.916 secs Elapsed
383.466 secs CPU time

Stderr.txt : not found
------------
Lunatics_x41zc_win32_cuda23.exe / PG1327_v7.wu :
AppName: Lunatics_x41zc_win32_cuda23.exe
AppArgs:
TaskName: PG1327_v7.wu
Started at : 20:04:55.190
Ended at : 20:07:02.123
126.881 secs Elapsed
19.672 secs CPU time
Speedup : 94.87%
Ratio : 19.49x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.98%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

------------
Lunatics_x41zc_win32_cuda32.exe / PG1327_v7.wu :
AppName: Lunatics_x41zc_win32_cuda32.exe
AppArgs:
TaskName: PG1327_v7.wu
Started at : 20:07:05.848
Ended at : 20:09:54.577
168.646 secs Elapsed
23.915 secs CPU time
Speedup : 93.76%
Ratio : 16.03x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.98%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

------------
Lunatics_x41zc_win32_cuda42.exe / PG1327_v7.wu :
AppName: Lunatics_x41zc_win32_cuda42.exe
AppArgs:
TaskName: PG1327_v7.wu
Started at : 20:09:57.918
Ended at : 20:12:59.450
181.477 secs Elapsed
17.769 secs CPU time
Speedup : 95.37%
Ratio : 21.58x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

------------
Lunatics_x41zc_win32_cuda50.exe / PG1327_v7.wu :
AppName: Lunatics_x41zc_win32_cuda50.exe
AppArgs:
TaskName: PG1327_v7.wu
Started at : 20:13:02.744
Ended at : 20:17:28.282
265.481 secs Elapsed
15.897 secs CPU time
Speedup : 95.85%
Ratio : 24.12x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.99%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

------------
Lunatics_x41zc_win32_cuda60.exe / PG1327_v7.wu :
AppName: Lunatics_x41zc_win32_cuda60.exe
AppArgs:
TaskName: PG1327_v7.wu
Started at : 20:17:31.613
Ended at : 20:23:09.800
338.128 secs Elapsed
16.661 secs CPU time
Speedup : 95.66%
Ratio : 23.02x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.29%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-PG1327_v7.wu.res
Result : Strongly similar, Q= 99.14%

------------
setiathome_7.00_windows_intelx86.exe -verb / refquick_v7.wu :
Result cached, skipping execution
94.740 secs Elapsed
92.119 secs CPU time

Stderr.txt : not found
------------
Lunatics_x41zc_win32_cuda23.exe / refquick_v7.wu :
AppName: Lunatics_x41zc_win32_cuda23.exe
AppArgs:
TaskName: refquick_v7.wu
Started at : 20:23:13.225
Ended at : 20:23:37.127
23.849 secs Elapsed
7.691 secs CPU time
Speedup : 91.65%
Ratio : 11.98x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.87%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.84%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.85%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.84%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.85%

------------
Lunatics_x41zc_win32_cuda32.exe / refquick_v7.wu :
AppName: Lunatics_x41zc_win32_cuda32.exe
AppArgs:
TaskName: refquick_v7.wu
Started at : 20:23:40.497
Ended at : 20:24:06.441
25.898 secs Elapsed
7.847 secs CPU time
Speedup : 91.48%
Ratio : 11.74x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.57%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.67%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.68%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.67%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.67%

------------
Lunatics_x41zc_win32_cuda42.exe / refquick_v7.wu :
AppName: Lunatics_x41zc_win32_cuda42.exe
AppArgs:
TaskName: refquick_v7.wu
Started at : 20:24:09.744
Ended at : 20:24:36.799
27.000 secs Elapsed
7.472 secs CPU time
Speedup : 91.89%
Ratio : 12.33x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.88%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.85%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.85%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.85%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.85%

------------
Lunatics_x41zc_win32_cuda50.exe / refquick_v7.wu :
AppName: Lunatics_x41zc_win32_cuda50.exe
AppArgs:
TaskName: refquick_v7.wu
Started at : 20:24:40.116
Ended at : 20:25:11.602
31.433 secs Elapsed
7.426 secs CPU time
Speedup : 91.94%
Ratio : 12.40x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.88%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.85%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.85%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.85%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.85%

------------
Lunatics_x41zc_win32_cuda60.exe / refquick_v7.wu :
AppName: Lunatics_x41zc_win32_cuda60.exe
AppArgs:
TaskName: refquick_v7.wu
Started at : 20:25:14.936
Ended at : 20:25:51.154
36.168 secs Elapsed
7.738 secs CPU time
Speedup : 91.60%
Ratio : 11.90x

R2: .\ref\ref-JG_setiathome_6.98_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.59%

R2: .\ref\ref-setiathome_6.97_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.68%

R2: .\ref\ref-setiathome_6.98p03_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.69%

R2: .\ref\ref-setiathome_6.98_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.68%

R2: .\ref\ref-setiathome_7.00_windows_intelx86.exe-refquick_v7.wu.res
Result : Strongly similar, Q= 99.68%


Claggy
ID: 1600423 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1600440 - Posted: 13 Nov 2014, 0:35:58 UTC - in response to Message 1600401.  
Last modified: 13 Nov 2014, 0:36:29 UTC

Have not gotten any seti GPU tasks for weeks, can anyone tell me why?
I have not changed any of my settings.
Running NVidia.

Is Boinc asking for Nvidia GPU work?

Double check your Setiathome project preferences and make sure 'Use Nvidia GPU' is still selected.

http://setiathome.berkeley.edu/prefs.php?subset=project

Claggy
ID: 1600440 · Report as offensive
Previous · 1 · 2

Message boards : Number crunching : gpu tasks - don't got any


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.