V10/11 of modified SETI MB CUDA + opt AP package for full multi-GPU+CPU use

[Raistmer]

Sorry, to make such a big deal. But it seems to me this GPU+CPU team, really slows things down. I mean it seems the GPU is really slowing down the cpu, and on a older computer the cpu is slowing down the GPU. Is there any way to make run on their own.
Thank you

No on both things.
But it wise to pair relative slow GPU with relative slow CPU if you have choice. Or, maybe, put all GPUs in one host. Feel free to try different variants, but reduce your work queue first. Trashing whole quad cache is not best way to go.

[Raistmer]

Here are updates to V10b for CPU part of team mods for x86 versions.
Now CPU app will not do attempts to re-schedule VLAR on GPU even if GPU is idle.
In multi-core systems it will allow another instance of CPU app that running non-VLAR task do re-schedule slightly later. So, total host performance should increase.

Thanks to Bob Mahoney who inspired this mod update.

ADDON: Be careful, it's UPDATE, not full pack. So don't delete anything from project directory, just update single exe file (or you will end with smth like posted below).

[attachment deleted by admin]

[elec999]

Here are updates to V10b for CPU part of team mods for x86 versions.
Now CPU app will not do attempts to re-schedule VLAR on GPU even if GPU is idle.
In multi-core systems it will allow another instance of CPU app that running non-VLAR task do re-schedule slightly later. So, total host performance should increase.

Thanks to Bob Mahoney who inspired this mod update.

Are the update I get
3/7/2009 08:46:31||Starting BOINC client version 6.4.7 for windows_intelx86
3/7/2009 08:46:31||log flags: task, file_xfer, sched_ops
3/7/2009 08:46:31||Libraries: libcurl/7.19.4 OpenSSL/0.9.8j zlib/1.2.3
3/7/2009 08:46:31||Running as a daemon
3/7/2009 08:46:31||Data directory: C:\Documents and Settings\All Users\Application Data\BOINC
3/7/2009 08:46:31||Running under account boinc_master
3/7/2009 08:46:31|SETI@home|[error] State file error: result 12ja09af.2025.890.14.8.226_1 is in wrong state
3/7/2009 08:46:31|SETI@home|[error] State file error: result 13ja09aa.24294.1299.4.8.242_0 is in wrong state
3/7/2009 08:46:31|SETI@home|[error] State file error: result 12ja09af.2025.890.14.8.228_0 is in wrong state
3/7/2009 08:46:31|SETI@home|[error] State file error: result 12ja09af.2025.26115.14.8.86_0 is in wrong state
3/7/2009 08:46:31|SETI@home|[error] State file error: result 12ja09af.2025.26524.14.8.135_0 is in wrong state
3/7/2009 08:46:31|SETI@home|[error] State file error: result 12ja09af.2025.26524.14.8.236_0 is in wrong state
3/7/2009 08:46:31||Processor: 4 GenuineIntel Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz [x86 Family 6 Model 15 Stepping 11]
3/7/2009 08:46:31||Processor features: fpu tsc sse sse2 mmx
3/7/2009 08:46:31||OS: Microsoft Windows XP: Professional x86 Editon, Service Pack 3, (05.01.2600.00)
3/7/2009 08:46:31||Memory: 2.00 GB physical, 3.85 GB virtual
3/7/2009 08:46:31||Disk: 69.23 GB total, 4.44 GB free
3/7/2009 08:46:31||Local time is UTC -5 hours
3/7/2009 08:46:31||Not using a proxy
3/7/2009 08:46:31||CUDA devices found
3/7/2009 08:46:31|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 4675326; location: home; project prefs: default
3/7/2009 08:46:31||General prefs: from SETI@home (last modified 06-Mar-2009 14:33:59)
3/7/2009 08:46:31||Computer location: home
3/7/2009 08:46:31||General prefs: no separate prefs for home; using your defaults
3/7/2009 08:46:31||Preferences limit memory usage when active to 1023.49MB
3/7/2009 08:46:31||Preferences limit memory usage when idle to 1637.58MB
3/7/2009 08:46:31||Preferences limit disk usage to 4.40GB
3/7/2009 08:46:31||Preferences limit # CPUs to 6
3/7/2009 08:46:31|SETI@home|Started upload of 12ja09af.27454.4980.13.8.105_1_0
3/7/2009 08:46:31|SETI@home|Started upload of 12ja09af.27454.26115.13.8.138_0_0
3/7/2009 08:46:31|SETI@home|Starting 12ja09af.2025.26524.14.8.232_1
3/7/2009 08:46:31|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:32|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:32|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:33|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:34|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:35|SETI@home|[error] Application file AK_v8b_win_SSSE3x_GPU_CPU_team_V10.exe missing signature
3/7/2009 08:46:35|SETI@home|[error] BOINC cannot accept this file
3/7/2009 08:46:35|SETI@home|Starting 12ja09af.2025.26524.14.8.225_0
3/7/2009 08:46:35|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:35|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:36|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:36|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:38|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:38|SETI@home|Starting 12ja09af.2025.26524.14.8.238_0
3/7/2009 08:46:38|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:39|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:39|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:39|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:40|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:40|SETI@home|Starting 13ja09aa.24294.5389.4.8.111_1
3/7/2009 08:46:40|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:40|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:40|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:41|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:41|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:41|SETI@home|Starting 13ja09aa.24294.5389.4.8.107_0
3/7/2009 08:46:41|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:42|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:42|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:43|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:44|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:44|SETI@home|Starting 13ja09aa.24294.5389.4.8.99_0
3/7/2009 08:46:44|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:44|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:44|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:44|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:44|SETI@home|[error] Process creation failed: Access is denied. (0x5)
3/7/2009 08:46:45|SETI@home|Computation for task 12ja09af.2025.26524.14.8.232_1 finished
3/7/2009 08:46:45|SETI@home|Output file 12ja09af.2025.26524.14.8.232_1_0 for task 12ja09af.2025.26524.14.8.232_1 absent
3/7/2009 08:46:45|SETI@home|Computation for task 12ja09af.2025.26524.14.8.225_0 finished
3/7/2009 08:46:45|SETI@home|Output file 12ja09af.2025.26524.14.8.225_0_0 for task 12ja09af.2025.26524.14.8.225_0 absent
3/7/2009 08:46:45|SETI@home|Computation for task 12ja09af.2025.26524.14.8.238_0 finished
3/7/2009 08:46:45|SETI@home|Output file 12ja09af.2025.26524.14.8.238_0_0 for task 12ja09af.2025.26524.14.8.238_0 absent
3/7/2009 08:46:45|SETI@home|Computation for task 13ja09aa.24294.5389.4.8.111_1 finished
3/7/2009 08:46:45|SETI@home|Output file 13ja09aa.24294.5389.4.8.111_1_0 for task 13ja09aa.24294.5389.4.8.111_1 absent
3/7/2009 08:46:45|SETI@home|Computation for task 13ja09aa.24294.5389.4.8.107_0 finished
3/7/2009 08:46:45|SETI@home|Output file 13ja09aa.24294.5389.4.8.107_0_0 for task 13ja09aa.24294.5389.4.8.107_0 absent
3/7/2009 08:46:45|SETI@home|Computation for task 13ja09aa.24294.5389.4.8.99_0 finished
3/7/2009 08:46:45|SETI@home|Output file 13ja09aa.24294.5389.4.8.99_0_0 for task 13ja09aa.24294.5389.4.8.99_0 absent
3/7/2009 08:46:51|SETI@home|Finished upload of 12ja09af.27454.26115.13.8.138_0_0
3/7/2009 08:46:51|SETI@home|Started upload of 12ja09af.27454.26115.13.8.152_0_0
3/7/2009 08:46:54|SETI@home|Finished upload of 12ja09af.27454.4980.13.8.105_1_0
3/7/2009 08:46:54|SETI@home|Started upload of 12ja09af.27454.26115.13.8.121_1_0
3/7/2009 08:46:55|SETI@home|Finished upload of 12ja09af.27454.26115.13.8.152_0_0
3/7/2009 08:46:55|SETI@home|Started upload of 12ja09af.27454.26115.13.8.166_0_0
3/7/2009 08:46:58|SETI@home|Finished upload of 12ja09af.27454.26115.13.8.121_1_0
3/7/2009 08:46:58|SETI@home|Started upload of 12ja09af.27454.26115.13.8.144_1_0
3/7/2009 08:46:59|SETI@home|Finished upload of 12ja09af.27454.26115.13.8.166_0_0
3/7/2009 08:47:01|SETI@home|Finished upload of 12ja09af.27454.26115.13.8.144_1_0
3/7/2009 08:47:56|SETI@home|Fetching scheduler list
3/7/2009 08:48:01|SETI@home|Master file download succeeded
3/7/2009 08:48:07|SETI@home|Sending scheduler request: Requested by user.  Requesting 1036805 seconds of work, reporting 109 completed tasks
3/7/2009 08:48:12|SETI@home|Scheduler request completed: got 0 new tasks
3/7/2009 08:48:12|SETI@home|Message from server: No work sent
3/7/2009 08:48:12|SETI@home|Message from server: No work is available for SETI@home Enhanced
3/7/2009 08:48:12|SETI@home|Message from server: (reached daily quota of 14 results)
3/7/2009 08:48:12|SETI@home|Message from server: (Project has no jobs available)
Thank you

[Raistmer]

Here are updates to V10b for CPU part of team mods for x86 versions.
Now CPU app will not do attempts to re-schedule VLAR on GPU even if GPU is idle.
In multi-core systems it will allow another instance of CPU app that running non-VLAR task do re-schedule slightly later. So, total host performance should increase.

Thanks to Bob Mahoney who inspired this mod update.

Are the update I get
3/7/2009 08:48:12|SETI@home|Message from server: No work sent
3/7/2009 08:48:12|SETI@home|Message from server: No work is available for SETI@home Enhanced
3/7/2009 08:48:12|SETI@home|Message from server: (reached daily quota of 14 results)
Thank you

It's good that only 14 tasks can be trashed now
What you did to recive such result? Probably deleted old app_info.xml ?
Or even tried to install update on host w/o V10 pack installed before ?

[cyclejon]

I got the same errors. Looking at it now, i forgot that i was still using v9. I upgraded to v10, using the update, and everything is working fine now.

[Raistmer]

I got the same errors. Looking at it now, i forgot that i was still using v9. I upgraded to v10, using the update, and everything is working fine now.

OMG, guys, please, think twice before trashing 10 days chaches, SETI servers already overloaded even w/o such actions.

The recommended way to do any (not only this one) update of opt apps:

1) DISABLE network access in BOINC
2) STOP BOINC
3) Copy BOINC whole data directory in another place as backup.
4) install update
5) start BOINC.
6) if all work fine - resume network access, else - stop BOINC and restore BOINC data folder from backup.

In other case you risk to trash whole your cache and be blamed by all few hundreds of your wingmans for that unfriendly action!

As failed result stated:
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
It means, your BOINC installation want to get this file but can't. You should already have it in project directory _before_ downloading work.
Either edit your app_info to point on another CUDA MB app you really try to install or download this stock version first.

[cyclejon]

I know, i hate losing the work. I only keep 2 days of work, didn't lose too much.

[RottenMutt]

Did you ever build on for older SSE2 AMD CPUs + a GPU?

What config do you have? For what CPU you need SSE2 app ?

Opteron 170/270/280 AMD

My 270's do sse3

Maybe his point is that sse2 runs faster.  i've lost 25% rac on my opteron rigs since switching.

[Raistmer]

Did you ever build on for older SSE2 AMD CPUs + a GPU?

What config do you have? For what CPU you need SSE2 app ?

Opteron 170/270/280 AMD

My 270's do sse3

Maybe his point is that sse2 runs faster.  i've lost 25% rac on my opteron rigs since switching.

SSE3_AMD runs faster than SSE2 on AMD.

[PatrickV2]

Here are updates to V10b for CPU part of team mods for x86 versions.
Now CPU app will not do attempts to re-schedule VLAR on GPU even if GPU is idle.
In multi-core systems it will allow another instance of CPU app that running non-VLAR task do re-schedule slightly later. So, total host performance should increase.

Thanks to Bob Mahoney who inspired this mod update.

ADDON: Be careful, it's UPDATE, not full pack. So don't delete anything from project directory, just update single exe file (or you will end with smth like posted below).

Any chances of x64 binaries?

Regards, Patrick.

[NudgeyNR]

Since installing V10 i am getting nothing but AP wu's, ideas

Untick AP in your SETI preferences.

Thanks didn't even think to look there

Have another question.

Can i run V10 opt apps along side an MW opt app ?

[Raistmer]

x64 SSSE3 & SSE3_Intel V10b updates added.
AMD users with x64 Windows should use SSE3_AMD x86 binary.


[attachment deleted by admin]

[elec999]

Is there a AMD x64 V10.
Thank you

[M_M]

 I guess GPU applications are still in early development stage and are not much optimized yet, since the GPU temps are still much lower (5-10C lower) then during some (GPU bound) games, and much, much lower (10-15C lower) then when running FurMark... GTX295 is in question.

Does anyone know for sure is there any work being done on SETI CUDA code optimization?

P.S. Big thanks to Raistmer, V10a(b) apps are working well and stable on my machine (WinXP 32bit, GTX295+Q9650, 6 apps running, 2GPUs and 4CPUs).

[Raistmer]

Probably it can be optimized more, but don't forget that CUDA doesn't use all hardware parts of GPU as GPU-intensive games do.
Any texture-related hardware hardly used here for example.