SETI@home v8 beta to begin on Tuesday

Message boards : News : SETI@home v8 beta to begin on Tuesday
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 45 · 46 · 47 · 48 · 49 · 50 · 51 . . . 99 · Next

AuthorMessage
Profile Sutaru Tsureku
Volunteer tester

Send message
Joined: 7 Jun 09
Posts: 285
Credit: 2,822,466
RAC: 0
Germany
Message 57742 - Posted: 9 Apr 2016, 14:22:04 UTC

Now it's:

Before the .vlar storm:
SETI@home v8 8.12 windows_intelx86 (opencl_ati5_SoG_nocal)
SETI@home v8 8.12 windows_intelx86 (opencl_ati_nocal)
SETI@home v8 8.12 windows_intelx86 (opencl_ati5_nocal)
- all these apps had an 'Average processing rate' of ~ 510.

SETI@home v8 8.12 windows_intelx86 (opencl_atiapu_SoG)
SETI@home v8 8.12 windows_intelx86 (opencl_atiapu_sah)
- all these apps had an 'Average processing rate' of ~ 300.

After the .vlar storm:
SETI@home v8 8.12 windows_intelx86 (opencl_ati5_SoG_nocal)
SETI@home v8 8.12 windows_intelx86 (opencl_ati_nocal)
SETI@home v8 8.12 windows_intelx86 (opencl_ati5_nocal)
- all these apps have now an 'Average processing rate' of ~ 250 to 300.
Less than above mentioned.

So now my PC work more with the slow 'opencl_atiapu_*' apps.


AFAIK, the tasks here go also into the data base for the science. These tasks at Beta aren't 'test' tasks.

@ Eric, what's correct? ('test' or 'real' tasks)

Thanks.
ID: 57742 · Report as offensive
Profile Raistmer
Volunteer tester
Avatar

Send message
Joined: 18 Aug 05
Posts: 2423
Credit: 15,878,738
RAC: 0
Russia
Message 57743 - Posted: 9 Apr 2016, 22:42:05 UTC - in response to Message 57742.  



So now my PC work more with the slow 'opencl_atiapu_*' apps.

Till time "VLAR storm" happened there were no good statistics to call APU builds definitely slower for your GPU (though quite possible they are).
All that APR thing too fluctuating, even w/o VLARs. It works in big numbers (maybe) but for single PC with active user offline benchmarking would be more effective eventually. APR from other side will serve to less active ones who will never run any benchmark by themselves.
News about SETI opt app releases: https://twitter.com/Raistmer
ID: 57743 · Report as offensive
Profile Mike
Volunteer tester
Avatar

Send message
Joined: 16 Jun 05
Posts: 2529
Credit: 1,074,556
RAC: 0
Germany
Message 57745 - Posted: 10 Apr 2016, 8:29:33 UTC

My offline benches have shown that APU versions are slightly faster on VLAR tasks but significantly slower on mid range tasks.
That should be the similar on FuryX.
With each crime and every kindness we birth our future.
ID: 57745 · Report as offensive
Profile Eric J Korpela
Volunteer moderator
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 15 Mar 05
Posts: 1546
Credit: 26,819,578
RAC: 427
United States
Message 57755 - Posted: 10 Apr 2016, 18:41:13 UTC - in response to Message 57745.  

I'll try to find a non-VLAR tape to get a better mix of work. Most of the GBT work from breakthrough will be VLAR. When Parkes observing happens, that could change, since the observing technique there is still under discussion.
ID: 57755 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 2 Jul 13
Posts: 505
Credit: 3,688,332
RAC: 349
United States
Message 57759 - Posted: 10 Apr 2016, 19:55:33 UTC - in response to Message 57755.  

Most of the GBT work from breakthrough will be VLAR...

:-(

I was trying different Apps with the VLARs the other day and found it appears the VLARs run better on NVs when the maxrregcount is set to 64 verses 32. Here's the difference between an App with it set to 32 and 64;
maxrregcount=32 http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=23549498
maxrregcount=64 http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=23549736
The only difference between those Apps is the maxrregcount.

maxrregcount here; http://setiathome.berkeley.edu/forum_thread.php?id=78569&postid=1772534#1772534
ID: 57759 · Report as offensive
Zalster
Volunteer tester

Send message
Joined: 30 Dec 13
Posts: 258
Credit: 12,167,465
RAC: 0
United States
Message 57764 - Posted: 11 Apr 2016, 3:37:35 UTC - in response to Message 57755.  

Most of the GBT work from breakthrough will be VLAR.


I still have hopes for Raistmer's OpenCl app, It makes good work of VLARs. And slightly faster with regular MBs
ID: 57764 · Report as offensive
Profile Raistmer
Volunteer tester
Avatar

Send message
Joined: 18 Aug 05
Posts: 2423
Credit: 15,878,738
RAC: 0
Russia
Message 57800 - Posted: 13 Apr 2016, 7:27:36 UTC

Can we have some "GUPPI" tasks here too?
News about SETI opt app releases: https://twitter.com/Raistmer
ID: 57800 · Report as offensive
Profile Jimbocous
Volunteer tester
Avatar

Send message
Joined: 9 Jan 16
Posts: 51
Credit: 1,038,205
RAC: 0
United States
Message 57801 - Posted: 13 Apr 2016, 7:54:19 UTC - in response to Message 57800.  

Can we have some "GUPPI" tasks here too?

Read my mind. Thanks.
Was wondering why no guppies have swum through here as yet?
If I can help out by testing something, please let me know.
Available hardware and software is listed in my profile here.
ID: 57801 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 2 Jul 13
Posts: 505
Credit: 3,688,332
RAC: 349
United States
Message 57814 - Posted: 13 Apr 2016, 16:10:51 UTC - in response to Message 57759.  

Most of the GBT work from breakthrough will be VLAR...

:-(

I was trying different Apps with the VLARs the other day and found it appears the VLARs run better on NVs when the maxrregcount is set to 64 verses 32. Here's the difference between an App with it set to 32 and 64;
maxrregcount=32 http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=23549498
maxrregcount=64 http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=23549736
The only difference between those Apps is the maxrregcount.

maxrregcount here; http://setiathome.berkeley.edu/forum_thread.php?id=78569&postid=1772534#1772534

Seems to be the same in Linux. The App compiled with maxrregcount=64 is much faster than the one with maxrregcount=32 with the Greenbank tasks.
maxrregcount=32 - http://setiathome.berkeley.edu/result.php?resultid=4855602154
WU true angle range is : 0.008804
Run time 45 min 58 sec
CPU time 2 min 27 sec
maxrregcount=64 - http://setiathome.berkeley.edu/result.php?resultid=4854499797
WU true angle range is : 0.008970
Run time 25 min 20 sec
CPU time 25 min 16 sec

I suppose the next step would be to compile a CUDA Baseline App with maxrregcount=64 and see how it preforms.
ID: 57814 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 2 Jul 13
Posts: 505
Credit: 3,688,332
RAC: 349
United States
Message 57817 - Posted: 13 Apr 2016, 18:22:46 UTC - in response to Message 57814.  

Most of the GBT work from breakthrough will be VLAR...

:-(

I was trying different Apps with the VLARs the other day and found it appears the VLARs run better on NVs when the maxrregcount is set to 64 verses 32. Here's the difference between an App with it set to 32 and 64;
maxrregcount=32 http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=23549498
maxrregcount=64 http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=23549736
The only difference between those Apps is the maxrregcount.

maxrregcount here; http://setiathome.berkeley.edu/forum_thread.php?id=78569&postid=1772534#1772534

Seems to be the same in Linux. The App compiled with maxrregcount=64 is much faster than the one with maxrregcount=32 with the Greenbank tasks.
maxrregcount=32 - http://setiathome.berkeley.edu/result.php?resultid=4855602154
WU true angle range is : 0.008804
Run time 45 min 58 sec
CPU time 2 min 27 sec
maxrregcount=64 - http://setiathome.berkeley.edu/result.php?resultid=4854499797
WU true angle range is : 0.008970
Run time 25 min 20 sec
CPU time 25 min 16 sec

I suppose the next step would be to compile a CUDA Baseline App with maxrregcount=64 and see how it preforms.

Oh well, seems the Baseline App with maxrregcount=64 will only get you halfway to the promised land.
It's better than maxrregcount=32 but falls short of the "Special" App;
http://setiathome.berkeley.edu/result.php?resultid=4855881066
WU true angle range is : 0.008804
Run time: 35 min 1 sec
CPU time: 2 min 14 sec
The second task was the same, http://setiathome.berkeley.edu/result.php?resultid=4855867410

As with Streams, it would seem maxrregcount=64 only works with Compute Code 3.2 and above;
ptxas warning : Too big maxrregcount value specified 64, will be ignored
ptxas info : 0 bytes gmem
ptxas info : Compiling entry function '_Z17cudaAcc_transposePfS_ii' for 'sm_20'
...
ptxas warning : Too big maxrregcount value specified 64, will be ignored
ptxas info : 0 bytes gmem
ptxas info : Compiling entry function '_Z17cudaAcc_transposePfS_ii' for 'sm_30'
...
ptxas info : 0 bytes gmem
ptxas info : Compiling entry function '_Z17cudaAcc_transposePfS_ii' for 'sm_32'
...
ptxas info : 0 bytes gmem
ptxas info : Compiling entry function '_Z17cudaAcc_transposePfS_ii' for 'sm_52'

There isn't a problem running the App on Devices lower than 3.2, the Compiler just ignores the setting on those Devices.
In Conclusion, to receive the best performance with VLARs on CUDA use the "Special" build with maxrregcount=64, but, 35 minutes is better than 45 minutes...
ID: 57817 · Report as offensive
Profile Sutaru Tsureku
Volunteer tester

Send message
Joined: 7 Jun 09
Posts: 285
Credit: 2,822,466
RAC: 0
Germany
Message 57822 - Posted: 14 Apr 2016, 2:06:25 UTC - in response to Message 57800.  
Last modified: 14 Apr 2016, 2:08:13 UTC

Raistmer wrote:
Can we have some "GUPPI" tasks here too?

You ask for 'guppi's...

And my PC get since 13 Apr 2016 ~13:30 UTC (since ~12 1/2 hours) just .vlar's...

;-)

:-(
ID: 57822 · Report as offensive
Zalster
Volunteer tester

Send message
Joined: 30 Dec 13
Posts: 258
Credit: 12,167,465
RAC: 0
United States
Message 57839 - Posted: 15 Apr 2016, 4:09:42 UTC - in response to Message 57822.  

Guppi are downloading to GPUs

Got a bunch of OpenCl_Nvidia_sah

Need to try the OpenCL_nvidia_SoG..
ID: 57839 · Report as offensive
Profile Dean
Volunteer tester

Send message
Joined: 11 Dec 14
Posts: 4
Credit: 2,985,448
RAC: 0
United States
Message 57855 - Posted: 16 Apr 2016, 10:30:09 UTC
Last modified: 16 Apr 2016, 10:33:40 UTC

Did some beta testing before shutting down due to the warmer season approaching. Found one that would not process on my AMD 7990. https://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=8503271

If someone could look into this, I would appreciate it.

Hope everyone enjoys the rest of spring and summer. See you all late in the fall.

And for those down under please stay warm.
ID: 57855 · Report as offensive
Richard Haselgrove
Volunteer tester

Send message
Joined: 3 Jan 07
Posts: 1444
Credit: 3,265,669
RAC: 0
United Kingdom
Message 57856 - Posted: 16 Apr 2016, 10:54:16 UTC - in response to Message 57855.  
Last modified: 16 Apr 2016, 11:02:44 UTC

Did some beta testing before shutting down due to the warmer season approaching. Found one that would not process on my AMD 7990. https://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=8503271

If someone could look into this, I would appreciate it.

ERROR: Possible wrong computation state on GPU, host needs reboot or maintenance

This seems to be a class of error which has recently been reported on the main project message boards (OpenCL NV MultiBeam v8 SoG edition for Windows) and is currently being investigated. Useful to know that it applies to AMD as well as NV cards, which perhaps supports the diagnosis by Raistmer in the linked post.

Edit - another copy of that WU - task 23617765 - failed on Urs Echternacht's Linux host without going through the temporary exit/retry cycle.
ID: 57856 · Report as offensive
zombie67 [MM]
Volunteer tester
Avatar

Send message
Joined: 18 May 06
Posts: 280
Credit: 26,237,012
RAC: 0
United States
Message 57857 - Posted: 16 Apr 2016, 13:06:32 UTC - in response to Message 55831.  

Message from server: NVIDIA GPU: Upgrade to the latest driver to process tasks using your computer's GPU


That's a long standing problem in BOINC. That message is gerenated whenever any GPU version requires a higher or lower driver revision, regardless of whether any versions can be run.


I just started getting this message with my nvidia card. So I upgraded to the highest version, 341.95. I think it was already there, but just to be sure. Still getting the message.

I guess this means the server is requiring a lower version. What is the lover version required?

Thanks!
Dublin, California
Team: SETI.USA

ID: 57857 · Report as offensive
Richard Haselgrove
Volunteer tester

Send message
Joined: 3 Jan 07
Posts: 1444
Credit: 3,265,669
RAC: 0
United Kingdom
Message 57859 - Posted: 16 Apr 2016, 14:01:44 UTC - in response to Message 57857.  

What is the lover version required?

Thanks!

Now there's an existential question, if ever I read one!

You don't need a new version at all. I guess you must be talking about host 78651. That GeForce 210 card is very old, and now on legacy bug-fix only driver support from NVidia - driver versions for newer cards are up to something like 364.72.

The tight driver restrictions the server is complaining about are for the OpenCL applications, and you wouldn't want to run them on legacy NVidia hardware anyway. The CUDA applications you were running - until you aborted three tasks a couple of days ago - were running just fine, and should continue to run with your current driver, if you let them.
ID: 57859 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 2 Jul 13
Posts: 505
Credit: 3,688,332
RAC: 349
United States
Message 57862 - Posted: 16 Apr 2016, 15:38:56 UTC - in response to Message 57856.  
Last modified: 16 Apr 2016, 15:47:13 UTC

Did some beta testing before shutting down due to the warmer season approaching. Found one that would not process on my AMD 7990. https://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=8503271

If someone could look into this, I would appreciate it.

ERROR: Possible wrong computation state on GPU, host needs reboot or maintenance

This seems to be a class of error which has recently been reported on the main project message boards (OpenCL NV MultiBeam v8 SoG edition for Windows) and is currently being investigated. Useful to know that it applies to AMD as well as NV cards, which perhaps supports the diagnosis by Raistmer in the linked post.

Edit - another copy of that WU - task 23617765 - failed on Urs Echternacht's Linux host without going through the temporary exit/retry cycle.

I also received Errors running the App SETI@home v8 v8.10 (opencl_ati5_SoG_nocal) in Linux; SIGSEGV: segmentation violation
This Task also failed with the same SIGSEGV Error, http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=23613396. When I tried running the task again to see if it gave the same Error, BOINC refused to upload the file complaining about it couldn't open the file. I suppose the results are being marked read only again. So, I aborted the upload and then received an Invalid even though it appears the task ran correctly the second time without giving the SIGSEGV Error. Running the tasks with an older App version doesn't produce any Errors, http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=76256
ID: 57862 · Report as offensive
zombie67 [MM]
Volunteer tester
Avatar

Send message
Joined: 18 May 06
Posts: 280
Credit: 26,237,012
RAC: 0
United States
Message 57863 - Posted: 16 Apr 2016, 20:16:34 UTC - in response to Message 57859.  

The CUDA applications you were running - until you aborted three tasks a couple of days ago - were running just fine, and should continue to run with your current driver, if you let them.


I have all GPU applications enabled in my preferences. Nothing has changed there. As you noticed, I was getting tasks no problem until recently. Now I am getting this error message from the server when I try to fetch work:

Message from server: NVIDIA GPU: Upgrade to the latest driver to process tasks using your computer's GPU


What changed on the server?
Dublin, California
Team: SETI.USA

ID: 57863 · Report as offensive
Richard Haselgrove
Volunteer tester

Send message
Joined: 3 Jan 07
Posts: 1444
Credit: 3,265,669
RAC: 0
United Kingdom
Message 57864 - Posted: 16 Apr 2016, 20:59:38 UTC - in response to Message 57863.  
Last modified: 16 Apr 2016, 21:00:06 UTC

They loaded a Green Bank Telescope data tape, which splits to mostly VLAR workunits. Those aren't sent to NVidia cards below Kepler (GTX 6xx). When data appropriate for processing on your hardware is available again, you will be eligible to receive it, despite what the message about driver versions is saying.
ID: 57864 · Report as offensive
zombie67 [MM]
Volunteer tester
Avatar

Send message
Joined: 18 May 06
Posts: 280
Credit: 26,237,012
RAC: 0
United States
Message 57865 - Posted: 16 Apr 2016, 21:30:54 UTC - in response to Message 57864.  

They loaded a Green Bank Telescope data tape, which splits to mostly VLAR workunits. Those aren't sent to NVidia cards below Kepler (GTX 6xx). When data appropriate for processing on your hardware is available again, you will be eligible to receive it, despite what the message about driver versions is saying.

Ah! Got it.

Curious, does this also apply to Intel HD graphics on OSX? They have also stopped getting tasks.
Dublin, California
Team: SETI.USA

ID: 57865 · Report as offensive
Previous · 1 . . . 45 · 46 · 47 · 48 · 49 · 50 · 51 . . . 99 · Next

Message boards : News : SETI@home v8 beta to begin on Tuesday


 
©2019 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.