Forum > GPU crunching

AK V8 + CUDA MB team work mod

<< < (13/51) > >>

FireGate_13:
I noticed the next strange things:
1. When MB_6.08_mod_CPU_team_CUDA.exe starts uses 100% of one core for about 1 minute.
2. I was surprised when I saw BOINC was crunching astropulse units I had stored in my pc even if I had installed correctly your mod. It used optimised ap_5.00r103_SSE3.exe so it is good..
3. I was confused when I saw 3 threads , 2 astropulse and one seti MB running on my 2 cores (AMD x2 5400+) and CUDA dissappeared from my task manager. the 2 AP were using 25% and seti_MB_cpu 50%.

I really would like to see which of three SETI_MB_wu's is using my GPU. Before it was written like this: (CUDA) in  boinc manager.
Thanks for your great mod! I love it!
My system is :
AMD x2 5400+(2.6Ghz) and nvidia 9800GT(oc'ed) and when my cpu had 11% done of two wu's my gpu had allready finished its first unit:D It's like it runs 10x faster!!!

Leopoldo:

--- Quote from: FireGate_13 on 01 Feb 2009, 09:28:58 am ---1. When MB_6.08_mod_CPU_team_CUDA.exe starts uses 100% of one core for about 1 minute.
--- End quote ---

It's just a sign about CUDA starting part


--- Quote ---3. I was confused when I saw 3 threads , 2 astropulse and one seti MB running on my 2 cores (AMD x2 5400+) and CUDA dissappeared from my task manager. the 2 AP were using 25% and seti_MB_cpu 50%.

I really would like to see which of three SETI_MB_wu's is using my GPU. Before it was written like this: (CUDA) in  boinc manager.

--- End quote ---

Did you miss Message 859062 from Raistmer at S@H forum?

i.e.


--- Quote ---"
How it works:
for BOINC it looks as usual CPU opt app installed. BOINC will call CPU app (AK_v8b_win_SSSE3x_GPU_CPU_team.exe in our case) and assign one of SETI MB tasks for it. But this app aware of possibility to use GPU for computations. It will check if another instance (it knows only itself and its clones, so - no other GPU-related projects please) already use GPU and if not - will start GPU-related app (MB_6.08_mod_CPU_team_CUDA.exe in our case) and suspend itself until GPU app finish. This CUDA app will do all work as usually but will do it on GPU leave CPU almost free.
"
So on single core you should see one working AK_v8, one suspended AK_v8 (0 CPU time and 0 % CPU usage) and one CUDA app.
--- End quote ---

Raistmer:

--- Quote from: FireGate_13 on 01 Feb 2009, 09:28:58 am ---1. When MB_6.08_mod_CPU_team_CUDA.exe starts uses 100% of one core for about 1 minute.
2. I was surprised when I saw BOINC was crunching astropulse units I had stored in my pc even if I had installed correctly your mod. It used optimised ap_5.00r103_SSE3.exe so it is good..
3. I was confused when I saw 3 threads , 2 astropulse and one seti MB running on my 2 cores (AMD x2 5400+) and CUDA dissappeared from my task manager. the 2 AP were using 25% and seti_MB_cpu 50%.

I really would like to see which of three SETI_MB_wu's is using my GPU. Before it was written like this: (CUDA) in  boinc manager.

--- End quote ---
1. It's OK, but not for min but ~half min (maybe for your system 60 secons is OK too).
2. Sure it will do AP tasks too, how do you think for what I included opt AP in package? ;)
3. how long did you see that? first 60 seconds (it's OK and no problem) or full task duration (it's bad and needs investigation)?

And about wich task using GPU - it's simple - look at stderr.txt in slots folders. BOINC will never say it using CUDA cause it doesn't know about it in this combo, I thought I described used algorithm in first post...

tpl:
Hi,
use notebook with 9700m gt but i can`t find nvidia driver 180.xx.
I find only 179.xx for Notebook...

Raistmer:

--- Quote from: tpl on 01 Feb 2009, 11:22:00 am ---Hi,
use notebook with 9700m gt but i can`t find nvidia driver 180.xx.
I find only 179.xx for Notebook...


--- End quote ---
Try to use some beta driver.... If you can;t upgrade to 18x.x it seems this modded app just not for your hardware/software still ( kick nVidia for new driver versions they should do that )

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version