Modified SETI MB CUDA + opt AP package for full GPU utilization

[Slawek]

ok working new APP on my GPU http://setiathome.berkeley.edu/result.php?resultid=1125694703
Time to incrased " Computer is connected to the Internet about every " 

1) oo  i change cc_config and now computing 3 AP ins. 2  ( i have 2 core + GPU ) ?

2) now i see computing 2 AP and CUDA ) the same time...   http://www.wrzuta.pl/obraz/ue2eHIWu7I/b2
 

[Slawek]

Some WU doing my GPU ~10 min and some 50-59 min, why so long? : CPU time is ~80-160 sec

This long time (50-59min ) is VLAR...hmm i think, but why to slow ?

[Richard Haselgrove]

Some WU doing my GPU ~10 min and some 50-59 min, why so long?

The true VLARs do indeed still take vastly longer than all the others (91 minutes, versus 22-23 minutes for mid range on my 9800GT - haven't had enough shorties to get an idea of the minimum).

The CUDA app is still acknowledged as a "work in progress" by the Berkeley developers: this is the first build where they actually got it to run right through to the end, at any speed. They are aware of the abysmal performance, but we don't know how long it'll take to come up with the next version.

[Raistmer]

BTW, if you feel current VLAR processing times too long for production app on main you could continue to use my V5b that will abotr VLARs and release task to be processed by another host possibly with CPU opt app (that will do processing much faster and effective). This is not perfect but some way of load balansing between CUDA/CPU in current conditions.

(I need some time to synch with threads now so sorry if this was proposed already).

[Slawek]

Hello ,

And this is my computing action 2 days http://setiathome.berkeley.edu/results.php?hostid=4708858



650 RAC now

CUDA

[Slawek]

No errors from this build  , working good

[Raistmer]

Fine. There is some validation problems remain, but probably they are pretty rare cases. Will see if beta testing will catch them again.

[Raistmer]

Here is new package version.
It contains the same CUDA part as before (equivalent to 6.08 stock with some mods) and latast opt AP SSE3 version (r103) )
This package will provide suboptimal performance in CUDA part versus V5b (because VLAR CUDA processing very inefficient now and V5b just abort VLAR tasks) but provides performance increase in CPU part because of opt AP rev103 increased performance.


[attachment deleted by admin]

[Raistmer]

And one more version.
Now changes in CUDA part of package. This build based on 6.08 sourses but with VLAR auto-kill mod enabled. It should provide best overall performance at cost of reissuing VLAR task to another host. NOT for using on SETI beta project.

[attachment deleted by admin]

[Slawek]

i have alot WU waiting  and ready for start and if i change new build i lost my cache WU ? i have 10 days in " Computer is connected to the Internet about every"

[Raistmer]

i have alot WU waiting  and ready for start and if i change new build i lost my cache WU ? i have 10 days in " Computer is connected to the Internet about every"

If you do right installation you should not lost any downloaded task.

[Slawek]

All tasks OK computing now

no errors

[Devaster]

if some one want here is cufft and cudart  dlls from last CUDA 2.1 final :

stop boinc unpack and replace in boinc data dirs the old  dlls

[attachment deleted by admin]

[sunu]

Is there an info page that explains what exactly

<avg_ncpus>0.0400</avg_ncpus>
<max_ncpus>0.0400</max_ncpus>

or any other options in app_info.xml do?

I'm trying to force 3+1 in a quad and whatever I do in app_info.xml (eg 1.0000 instead of 0.0400) has no effect.

Maybe it is a boinc thing in linux?

[The Grinch]

I don't know if this will helps you

http://boinc.berkeley.edu/wiki/Anonymous_platform