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

Forum > GPU crunching

<< < (2/80) > >>

Raistmer:

--- Quote from: gaulois952 on 26 Feb 2009, 03:10:29 am ---I only have that in my cc_config

<cc_config>
<log_flags>
</log_flags>
<options>
<dont_contact_ref_site>1</dont_contact_ref_site>
</options>
</cc_config>


Help me :(

--- End quote ---
If you don't understand cc_config structure just replace your with that from first post. And don't forget to replace yellow line with acual number.

Leopoldo:

--- Quote from: Raistmer on 24 Feb 2009, 06:56:31 pm ---When you post to this thread seeking for help, please, don't forget to provide link on your host and description of your config (OS, number of GPU cards, what pack you use, video driver version).
It will wastly decrease number of unneeded questions and save time both for you and anyone who will help you.

--- End quote ---

Hello, Raistmer!

My computer http://setiathome.berkeley.edu/show_host_detail.php?hostid=4632306 works with Win2003 32-bit, Core2Duo, 1 GPU 9600GT, drv 182.06, BM 6.6.11, ncpus=3

I'm doing micromanagement of task queue at Boinc Manager everyday as You supposed at http://lunatics.kwsn.net/gpu-crunching/ak-v8-cuda-mb-team-work-mod.msg13293.html#msg13293 (1 - Suspend all tasks; 2 - resume non-VLAR task; 3 - resume VLAR tasks)

For my 2-core system normal behaviour is 3 copies of AK_... (2 running + 1 idle) and 1 copy of MB_...

Previous team packs worked as described above. But situation changed with new V10a pack! Every suspending of one running task and resuming of other task leads to one more copy of remaining in memory process "AK_v8b_win_SSSE3x_GPU_CPU_team_V10.exe".

I.e. if I wants to reassign one CPU-task to VLAR, I'll do suspending all not-running tasks, then suspending one chosen CPU-task, then resuming one VLAR-task. After this I can see in memory already 4 copies of AK_... (2 running, 2 idle) and 1 copy of MB_... Next suspendig/resuming leads to 5 copies of AK_... (2 running + 3 idle) and 1 copy of MB_...

Suspending/resuming of whole SETI@Home project isn't helps to remove useless copies, only BM restarting helps. What am I doing wrong?

P.S. V8 had no such behaviour.

[edit]Such behaviour isn't easily repeatable - i.e. not each reassign leads to remaining copies of AK_... It is sporadically. So far I can't reproduce it[/edit]

P51 Mustang:
My computer has been throwing a lot of computation errors since I started using V10a x64. I went from V8 to V10a to get the new AP units. It is a Quad core running Vista 64 bit with driver 181.22 with a single GeForce 8500 GT.

Some of the errors are the VLAR kill, but most of them are not. Here hs a link to a workunit that is throwing the computation error.

http://setiathome.berkeley.edu/result.php?resultid=1173667098

Raistmer:

--- Quote from: Leopoldo on 26 Feb 2009, 07:11:31 am ---
--- Quote from: Raistmer on 24 Feb 2009, 06:56:31 pm ---When you post to this thread seeking for help, please, don't forget to provide link on your host and des#biption of ur config (OS, number of GPU cards, what pack you use, video driver version).
It will wastly decrease number of unneeded questions and save time both for you and anyone who will help you.

--- End quote ---

Hello, Raistmer!

My computer http://setiathome.berkeley.edu/show_host_deTAil.php?hostid=4632306 works with Win2003 32-bit, Core2Duo, 1 GPU 9600GT, drv 182.06, BM 6.6.11, ncpus=3

I'm ›ing micromanagement of task queue at Boinc Manager everyday as You supposed at http://lunatics.kwsn.net/gpu-crunching/ak-v8-cuda-mb-team-work-mod.msg13293.html#msg13293 (1 - Suspend all tasks; 2 - resume non-VLAR task; 3 - resume VLAR tasks)

For my 2-core system normal behaviour is 3 copies of AK_... (2 running + 1 idle) and 1 copy of MB_...

Previous team packs worked as described above. But situation changed with new V10a pack! Every suspending of one running task and resuming of other task leads to one more copy of remaining in memory process "AK_v8b_win_SSSE3x_GPU_CPU_team_V10.exe".

I.e. if I wants to reassign one CPU-task to VLAR, I'll do suspending all not-running tasks, then suspending one chosen CPU-task, then resuming one VLAR-task. After this I can see in memory already 4 copies of AK_... (2 running, 2 idle) and 1 copy of MB_... Next suspendig/resuming leads to 5 copies of AK_... (2 running + 3 idle) and 1 copy of MB_...

Suspending/resuming of whole SETI@Home project isn't helps to remove useless copies, only BM restarting helps. What am I doing wrong?

P.S. V8 had no such behaviour.

[edit]Such behaviour isn't easily repeatable - i.e. not each reassign leads to remaining copies of AK_... It is sporadically. So far I can't reproduce it[/edit]

--- End quote ---

Only ones that hold CUDA MB process should behave so.
CUDA MB will reject to stop now reducing probability that BOINC (or user ;) ) making wrong decision and tries to leave GPU idle by running CPU-only apps.
So long as least single SETI MB task running (for single GPU host) SETI MB team can do its GPU scheduling w/o additional help from user.

Raistmer:

--- Quote from: P51 Mustang on 26 Feb 2009, 08:50:33 am ---My computer has been throwing a lot of computation errors since I started using V10a x64. I went from V8 to V10a to get the new AP units. It is a Quad core running Vista 64 bit with driver 181.22 with a single GeForce 8500 GT.

Some of the errors are the VLAR kill, but most of them are not. Here is a link to a workunit that is throwing the computation error.

http://setiathome.berkeley.edu/result.php?resultid=1173667098

--- End quote ---
try to revert to old DLL versions (from older packs or stock).
Lookd like driver/CUDA runtime problem... If with same DLL/driver set stock app doesn't show such errors, report again please.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version