Message boards :
Number crunching :
GBT ('guppi') .vlar tasks will be send to GPUs, what you think about this?
Message board moderation
Previous · 1 . . . 4 · 5 · 6 · 7 · 8 · 9 · 10 · Next
Author | Message |
---|---|
jason_gee Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0 |
Also supposedly better equipped for longer simpler serial workloads (e.g. bitcoin mining) "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. |
tullio Send message Joined: 9 Apr 04 Posts: 8797 Credit: 2,930,782 RAC: 1 |
In SETI Beta I saw that guppi .vlars crunched with atiapu_SoG on my Linux box with an AMD HD 7770 take twice the time of those crunched with ati5_cal132 and get the double of credits. I have reported, even if in the wrong place. I enlisted in SETI Beta because I had read that guppi .vlar were sent to GPUs only there and not to SETI@home. Now I see them also here and I am crunching them on my Windows PC with its GTX 750 Ti OC. I have no experience with graphic boards, I am using mostly Virtual Box in the CERN projects, where I was an Alpha tester since November 2010. Tullio |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
So you probably get used to post links to original data in discussion? Links to results in current discussion to analyse? |
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
Something I just noticed, and this may have something to do with it. After rebuilding this computer because of some file corruption preventing me from doing a backup of the system, I now have both CUDA50 and CUDA42 WUs running at the same time. IF this is incorrect, How do I correct it? Both CUDAs seem to be running to completion just fine. This computer: http://setiathome.berkeley.edu/results.php?hostid=7965534 SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
IF this is incorrect, How do I correct it? Both CUDAs seem to be running to completion just fine. This computer: http://setiathome.berkeley.edu/results.php?hostid=7965534 It's perfectly correct for stock setup. |
tullio Send message Joined: 9 Apr 04 Posts: 8797 Credit: 2,930,782 RAC: 1 |
Then tell me what I had to do. Tullio |
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
IF this is incorrect, How do I correct it? Both CUDAs seem to be running to completion just fine. This computer: http://setiathome.berkeley.edu/results.php?hostid=7965534 I guess I did not realize it was stock as I thought I had downloaded and installed the Lunatics Installer. Can I just run the installer now? SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Then tell me what I had to do. Locate tasks you talk about and provide links to them on beta webpage. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
IF this is incorrect, How do I correct it? Both CUDAs seem to be running to completion just fine. This computer: http://setiathome.berkeley.edu/results.php?hostid=7965534 Yes, but OpenCL GPU apps need to be updated to rev 3430 after that from my cloud repo. |
johnnymc Send message Joined: 5 May 99 Posts: 36 Credit: 9,138,623 RAC: 0 |
My GTX 960 is handling: one non gbt at 56% gpu usage 20-25 minutes crunch time two non gbt at 78% gpu usage pretty close to the same time each thr non gbt at 99% gpu usage but seems to take them 90 minutes each. Once the GBT vlars came in I had to crunch one work unit at a time. Two of these running concurrent took about an hour ten minutes each with gpu pegged at 99%. One at a time takes 25-35 minutes each with gpu usage 97-98%. ~ Life's short; make fun of it. User ID: 39750; SETI@home member since: 5 May 1999; Classic workunits: 5,851; Classic CPU time: 108,169 hours |
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
I ran the Lunitics installer and now the memory usage on the GPU is much more constant. Where do I find the rev 3430? SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
Mike Send message Joined: 17 Feb 01 Posts: 34362 Credit: 79,922,639 RAC: 80 |
http://mikesworldnet.de/download.html With each crime and every kindness we birth our future. |
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
Thanks, I could not find it because IE decided to show me your page from the temp file, not the new page. I did a refresh and it was there as it should be. SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13841 Credit: 208,696,464 RAC: 304 |
So while all the crunching work should be done on the GPU, but at present it isn't. And then , when communication CPU<=>GPU really decreased, "my BOINC doesn't tick " appears... So ideally that communication should be asynchronous. Every 100th, 10th (half, even whole second) the GPU outputs it's progress on the WU until it's complete at which time it sends out the result file and requests another WU. The GPU isn't waiting on any CPU responses (until it requests another WU), and the CPU can do with the progress updates whatever it needs to (update the progress bar or ignore it as too recent since last update or whatever). If while the WU is being processed the CPU doesn't receive any updates on the progress of the WU, then it initiates a call to the GPU to find out what's going on. Grant Darwin NT |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Ah, you strongly know how it "should be", fine, we have new optimiztion team member it seems, with fresh and great ideas. Good, you can start here: https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13841 Credit: 208,696,464 RAC: 304 |
Ah, you strongly know how it "should be", fine, we have new optimiztion team member it seems, with fresh and great ideas. Good, you can start here: https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt If only I had even an ounce of ability... Grant Darwin NT |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Ah, you strongly know how it "should be", fine, we have new optimiztion team member it seems, with fresh and great ideas. Good, you can start here: https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt So, all this just wishful thinking and theoretical speculations about? Then I could tell not how it "should" but how it "does". It doesn't help. Both from thechnical and human resources point of view. |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13841 Credit: 208,696,464 RAC: 304 |
Ah, you strongly know how it "should be", fine, we have new optimiztion team member it seems, with fresh and great ideas. Good, you can start here: https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt Curiosity pure & simple, about why an application running on a GPU is so dependant on CPU resources. Grant Darwin NT |
RueiKe Send message Joined: 14 Feb 16 Posts: 492 Credit: 378,512,430 RAC: 785 |
|
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Ah, you strongly know how it "should be", fine, we have new optimiztion team member it seems, with fresh and great ideas. Good, you can start here: https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt Cause GPU and CPU are different devices and GPU constitutes coprocessor, not Central Processing Unit. EDIT: and cause "aplication running on GPU" is misleading jargon. Application is running on CPU always. That's the way modern PC architecture works and that's why only one device in PC called CPU. |
©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.