Forum > GPU crunching

CPU <-> GPU rebranding

<< < (50/75) > >>

MarkJ:

--- Quote from: rx780 on 04 Oct 2009, 02:10:35 am ---So the client_state.xml2009* files are created when run rebrand without shutting down Boinc? These files can be safely deleted? (Assuming boinc shut down )

--- End quote ---

You don't have to shut it down as long as you leave the original client_state and client_state_prev file alone.

The client_state yyyyymmdd ones are backup copies of client_state before Reschedule changes the wu information and BOINC doesn't use these.

timiman:
I agree. You dont know when you are going to need any previous client_state.xml file... :(

Franz:
I should like to know why I have two PCs, ... same cpu, os, boinc level, otopmized apps (using unified same installer), cuda (one 250 and other 260) but in one I get only 5.28 (so I can't use reschedule) and in the other I get only 6.03 (so I can use reschedule).
Tell me how I can get 6.03 (prayers, ...  mantra, ... software?)

FF

Josef W. Segur:

--- Quote from: Franz on 24 Oct 2009, 03:45:55 pm ---I should like to know why I have two PCs, ... same cpu, os, boinc level, otopmized apps (using unified same installer), cuda (one 250 and other 260) but in one I get only 5.28 (so I can't use reschedule) and in the other I get only 6.03 (so I can use reschedule).
Tell me how I can get 6.03 (prayers, ...  mantra, ... software?)

FF
--- End quote ---

Add or fix the section in the app_info.xml file which says you have a 6.03 compliant application installed. The BOINC core client assigns CPU work to the highest numbered CPU application it knows about.

Post the app_info.xml here if you'd like more specific advice.
                                                                                Joe

Franz:
my app_info.xml must be the standard one, build by the last  lunatics unified installer.
what else?


--- Code: --- <app_info>
-
<app>
<name>setiathome_enhanced</name>
</app>
-
<file_info>
<name>AK_v8b_win_SSSE3x.exe</name>
<executable/>
</file_info>
-
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
-
<file_ref>
<file_name>AK_v8b_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
-
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
-
<file_ref>
<file_name>AK_v8b_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
-
<app>
<name>astropulse_v5</name>
</app>
-
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
-
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
-
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
-
<app>
<name>astropulse_v505</name>
</app>
-
<file_info>
<name>ap_5.05r168_SSE3.exe</name>
<executable/>
</file_info>
-
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
-
<file_ref>
<file_name>ap_5.05r168_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
-
<app>
<name>setiathome_enhanced</name>
</app>
-
<file_info>
<name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</name>
<executable/>
</file_info>
-
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
-
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
-
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
-
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<plan_class>cuda</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
-
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
-
<file_ref>
<file_name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</file_name>
<main_program/>
</file_ref>
-
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
-
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
-
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
</app_info>
--- End code ---

Navigation

[0] Message Index

[#] Next page

[*] Previous page