More than one WU per GPU at the same time ?

Only if you use app_info.xml and know how to edit it.

(your computers are hidden so you have to help yourself, we can't see what hardware you have and it's pain to ask for every detail)


____________



- ALF - "Find out what you don't do well ..... then don't do it!" :)

Your GeForce GTX 480 (1503MB) can run 2 or 3 tasks at the same time (don't try this with GeForce GT 220 - it can't)

You are using app_info.xml created by Lunatics' Unified Installer v0.37
so you can edit it with Notepad to change every occurrence (probably 6 places) of:

GPU Temp : up from 42°C to 44°C

Do i have to change anything if there will be a second GTX 480 ?

Is the use of Lunatics' Unified Installer only way to run multiple WU per GPU?
____________

AFAIK the only way is to use app_info.xml no matter is it created by Lunatics' Unified Installer or manually.

Maybe the future versions of BOINC will have some option to choose the number of simultaneous tasks/GPU on per-project basis.


____________



- ALF - "Find out what you don't do well ..... then don't do it!" :)

3 GPU WU's :
GPU Load : 100 %
Mem Used : 998 MB

Your GeForce GTX 480 (1503MB) can run 2 or 3 tasks at the same time (don't try this with GeForce GT 220 - it can't)

...and on a completely different note, i'm familiar with Multibeam/Enhanced tasks and Astropulse tasks, but what are VLAR tasks? and are there other types of tasks in addition to these 3?

VLAR stands for Very Low Angle Range, as opposed to Very High Angle Range (VHAR), of MultiBeam tasks. So, there are only two types of tasks (with various subtypes).

Gruß,
Gundolf

For ATI you do. Nvidia GPU's aren't able to run AP WU's at present
____________
Proud member of TSWB.

End terrorism by building a school

Your GeForce GTX 480 (1503MB) can run 2 or 3 tasks at the same time (don't try this with GeForce GT 220 - it can't)

Bill, is this simultaneous task assessment based on the memory capacity of the GPU? and if so, why can't the OP's GTX 480 run a 4th simultaneous task if 3 tasks are only using up ~1GB of GPU memory and he has ~500MB still available?

VLAR stands for Very Low Angle Range, as opposed to Very High Angle Range (VHAR), of MultiBeam tasks. So, there are only two types of tasks (with various subtypes).

Gruß,
Gundolf

thanks for clearing that up Gundolf. so do AP tasks have sub-types as well, or is it just the MB tasks?

The number of tasks per GPU is determined by try and success/error.

People try first 2 simultaneous tasks - if they both finish in less total time compared to 2 consecutive tasks you have success (and may try 3).
At one point (e.g. 4 tasks) you will notice that they fight for GPU/RAM resources and run too slow (e.g. 3 tasks finish in 2 hours (40 min/task) and 4 in 4 hours (60 min/task))

GPU load is good indicator - if you see 60% with 2 tasks you may try 3 to get 90-95% GPU load (but if you see 90% with 2 tasks the GPU is unlikely to handle more tasks)

So by experimenting people found that Fermi can run 2-3 tasks (GF 460-480) but e.g. GF 275 have enough load with only 1 task and is less effective with 2 tasks.

Do your own experiments monitoring the GPU load, temperature and result production (tasks/day) and find the limits (optimum) of your GPU/VideoRAM

i'm hoping TOM will chime in, b/c i'm not sure how he was able to tell that his GPU memory consumption was 998MB.

but is blanking literally to Astropulse what angle width is to Multibeam? in other words, does percent blanking have to do with the angle width of a survey that generates AP WUs?

...had no luck with the older versions GPU-Z. so it must just be a feature GPU-Z only makes available for nVidia GPUs and not ATI GPUs. i wonder if there is any other software out there that does allow ATI users to monitor their GPU memory usage?


also, i tried running 2 S@H GPU tasks simultaneously on the 5870, and while BOINC allowed it without errors, only 1 task was actually making progress even though both task's run times were ticking away. i wasn't expecting it, but after changing the app_info.xml file back to "run 1 task at a time" and restarting BOINC, the other task that made 0% progress no longer had 4:25 of run time on the clock and was being shown as "ready to start," which is nice to say the least b/c i didn't get an error. but this does seem odd. on the other hand, my GPU usage hovers at 90+% while crunching only 1 S@H GPU task, so perhaps that's why it isn't taking on more simultaneous work, even when BOINC and/or the application itself is instructed to allow it. is this normal for an ATI GPU? are nVidia GPUs known to be more efficient than ATI GPUs when it comes to crunching S@H MB and AP?
____________

...had no luck with the older versions GPU-Z. so it must just be a feature GPU-Z only makes available for nVidia GPUs and not ATI GPUs. i wonder if there is any other software out there that does allow ATI users to monitor their GPU memory usage?


also, i tried running 2 S@H GPU tasks simultaneously on the 5870, and while BOINC allowed it without errors, only 1 task was actually making progress even though both task's run times were ticking away. i wasn't expecting it, but after changing the app_info.xml file back to "run 1 task at a time" and restarting BOINC, the other task that made 0% progress no longer had 4:25 of run time on the clock and was being shown as "ready to start," which is nice to say the least b/c i didn't get an error. but this does seem odd. on the other hand, my GPU usage hovers at 90+% while crunching only 1 S@H GPU task, so perhaps that's why it isn't taking on more simultaneous work, even when BOINC and/or the application itself is instructed to allow it. is this normal for an ATI GPU? are nVidia GPUs known to be more efficient than ATI GPUs when it comes to crunching S@H MB and AP?