How do I know that the task is running under CUDA?

Questions and Answers : GPU applications : How do I know that the task is running under CUDA?
Message board moderation

To post messages, you must log in.

AuthorMessage
NewtonianRefractor
Volunteer tester
Avatar

Send message
Joined: 19 Sep 04
Posts: 495
Credit: 225,412
RAC: 0
United States
Message 841736 - Posted: 19 Dec 2008, 0:47:53 UTC

By looking at Boinc manager, how do I know that a task is running with CUDA?
ID: 841736 · Report as offensive
OzzFan Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Apr 02
Posts: 15691
Credit: 84,761,841
RAC: 28
United States
Message 841746 - Posted: 19 Dec 2008, 1:06:32 UTC

In the Tasks tab under BOINC Manager, under the Application field it will say CUDA.
ID: 841746 · Report as offensive
Profile The Mad Banger
Volunteer tester
Avatar

Send message
Joined: 6 May 07
Posts: 26
Credit: 577,038
RAC: 0
United States
Message 848220 - Posted: 2 Jan 2009, 15:55:36 UTC - in response to Message 841746.  

On my machine - no tasks ever mention CUDA - yet, sometimes, they get done - they never show under tasks
ID: 848220 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 848227 - Posted: 2 Jan 2009, 16:02:52 UTC - in response to Message 848220.  

How do you know for sure? Are you keeping an eye on BOINC Manager 24 hours a day?

Anyway, it'll tell in the Tasks tab in Advanced View that it's using 0.03 CPU + CUDA
ID: 848227 · Report as offensive
Don

Send message
Joined: 8 Aug 01
Posts: 1
Credit: 13,151,750
RAC: 6
United States
Message 853250 - Posted: 14 Jan 2009, 6:44:00 UTC

just upgraded to boinc 6.4.5 widget 2.8.7 and am running an AMD 3200 and NVIDIA 8500gt on XP Pro SP3 system. When I upgraded new benchmarks ran and CUDA was discovered but task panel doesn't show any other tasks running other than my 1 project for my 1 cpu. I re benchmarked and only found 1 cpu no CUDA? Ideas?
ID: 853250 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 853281 - Posted: 14 Jan 2009, 10:14:14 UTC - in response to Message 853250.  

The GPU isn't benchmarked. So when you run benchmarks in BOINC, it'll only benchmark the CPU.
ID: 853281 · Report as offensive
Maik

Send message
Joined: 15 May 99
Posts: 163
Credit: 9,208,555
RAC: 0
Germany
Message 853299 - Posted: 14 Jan 2009, 12:36:39 UTC
Last modified: 14 Jan 2009, 13:19:13 UTC

NewtonianRefractor wrote:
By looking at Boinc manager, how do I know that a task is running with CUDA?


do i have a cuda device? (Meldungen = messages)


is Cuda running? (Aufgaben = tasks)

ID: 853299 · Report as offensive
Alexboy456

Send message
Joined: 20 Oct 05
Posts: 21
Credit: 192,446
RAC: 0
United Kingdom
Message 853309 - Posted: 14 Jan 2009, 13:24:15 UTC

I have a laptop with the cuda devices and it is no longer using the GPU. what could be causing this?

I have uninstalled/reinstalled bionic and reinstalled latest nvidia drivers. the prefrences on the web have it set to use gpu when available. is this something to do with seti or is it a laptop issue?
ID: 853309 · Report as offensive
Profile Leopoldo
Volunteer tester
Avatar

Send message
Joined: 4 Aug 99
Posts: 102
Credit: 3,051,091
RAC: 0
Russia
Message 853314 - Posted: 14 Jan 2009, 13:36:59 UTC - in response to Message 853309.  
Last modified: 14 Jan 2009, 14:02:11 UTC

Today my BOINC downloaded stock old non-CUDA application v6.03 and all new WUs indicates 6.03 too.
Maybe CUDA applucation has been set back to beta state and all newly generated WUs locked to non-CUDA application 6.03 - then BOINC will download no more CUDA WUs...
ID: 853314 · Report as offensive
Maik

Send message
Joined: 15 May 99
Posts: 163
Credit: 9,208,555
RAC: 0
Germany
Message 853316 - Posted: 14 Jan 2009, 13:38:06 UTC
Last modified: 14 Jan 2009, 13:38:23 UTC

what are you seeing in your bm-log?

this:
|SETI@home|Sending scheduler request: To fetch work. Requesting 300369 seconds of work, reporting 0 completed tasks

or this:
|SETI@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks
ID: 853316 · Report as offensive
Alexboy456

Send message
Joined: 20 Oct 05
Posts: 21
Credit: 192,446
RAC: 0
United Kingdom
Message 853324 - Posted: 14 Jan 2009, 13:56:36 UTC - in response to Message 853316.  

i am getting this

SETI@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks

i have 2 WU rinning ATM and 2 waiting.

they are all SETI@home Enhanced 6.03.

i have 3 pcs doing this and they are all using 6.03

1 has a cuda vga card and the others are xeon cpus
ID: 853324 · Report as offensive
Maik

Send message
Joined: 15 May 99
Posts: 163
Credit: 9,208,555
RAC: 0
Germany
Message 853376 - Posted: 14 Jan 2009, 16:18:06 UTC
Last modified: 14 Jan 2009, 16:29:35 UTC


  • a) If BM request 0 secends of work you will not get any work.
  • b) If BM requests 0 seconds of work

    • 1 then the BM noticed in your tasklist is enough work how you have set (in settings for cache in account prefs)
    • 2 you have set the project to NNT (no new tasks)
    • 3 you have suspended tasks in your task list


  • c) If version 6.03 is shown you wont get your gpu to work, the newest cuda-application has version 6.07
    Maybe you could try a manual install with a modded version from lunatics


ID: 853376 · Report as offensive
Maik

Send message
Joined: 15 May 99
Posts: 163
Credit: 9,208,555
RAC: 0
Germany
Message 853383 - Posted: 14 Jan 2009, 16:53:24 UTC
Last modified: 14 Jan 2009, 16:59:35 UTC

Ok, i found someting on beta bord.
It seems that there is a serverside config 'who get cuda-tasks, who not'
read here

short version: if your cuda-enabled graphic card is to weak you wont get the MB-Cuda-App
thats surely one of the ways to fix the VLAR problem
ID: 853383 · Report as offensive
Alexboy456

Send message
Joined: 20 Oct 05
Posts: 21
Credit: 192,446
RAC: 0
United Kingdom
Message 853722 - Posted: 15 Jan 2009, 9:06:39 UTC

thanks for the info. i was using the cuda prcessing. for some reason it gust stopped and started on the enhanced 6.03 stuff. the laptop is a macbook pro running windows with the latest nvidia drivers. the gpu is a geforce 9600m GT. it is found when bionic starts. i have tried the latest version of bionic as well as the beta
ID: 853722 · Report as offensive
Paul DT Scully
Volunteer tester
Avatar

Send message
Joined: 30 Jun 04
Posts: 26
Credit: 259,861
RAC: 0
United Kingdom
Message 854011 - Posted: 16 Jan 2009, 1:07:10 UTC - in response to Message 853722.  

I was not downloading any WU's, then I disabled "Use Graphics Processing Unit (GPU) if available" settings in SETI@home preferences, and now it has downloaded the 6.07 cuda WU's....what gives?

I only disabled it because Seti Cuda was causing my other GPU projects to crash... GPUGRID ran fine, when I suspended seti...but when I resumed...seti would crash, followed by GPUGrid.

Why can't seti get CUDA to work like GPUGrid seem able to do...?
Q6600 @ 2.40GHz
Vista Ultimate x64 SP1
Mem: 4GB
8800GT 181.22
BOINC 6.6.3 Win64

ACTIVE PROJECTS
ID: 854011 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 854106 - Posted: 16 Jan 2009, 7:04:02 UTC - in response to Message 854011.  
Last modified: 16 Jan 2009, 7:04:13 UTC

Why can't seti get CUDA to work like GPUGrid seem able to do...?

You think that GPUGrid went from nothing to working applications overnight on the 17th of December 2008? Or perhaps because they've been at it already since July 17, 2008?
ID: 854106 · Report as offensive

Questions and Answers : GPU applications : How do I know that the task is running under CUDA?


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