Forum > GPU crunching

CPU <-> GPU rebranding

<< < (52/75) > >>

Franz:

--- Quote from: Josef W. Segur on 27 Oct 2009, 12:44:51 pm ---I'm stumped for now, but will think about it some more.
                                                                              Joe

--- End quote ---
Just some more info
1) now on both hosts I have installed Boinc Manager 6.6.41
2) on the host receiving only 5.28 I run boincview.exe and (sometimes) BoincTasks.
This last one can manage Day Work and Wanted WU .... so I think that can be involved in the problem
In any case I have not filled those fields with data.
FF

Josef W. Segur:
The primary server-side change is that the Scheduler now tells the client to use what it considers the "best" app version. What it considers "best" doesn't consider the version number. Instead it just takes the suitable app versions in order, and chooses the one with the highest flops rating. If the flops are equal, the first suitable app is considered "best".

It's possible that simply listing the higher numbered version first in the app_info.xml would help, but that doesn't explain why the current order works on some hosts but not others.

Franz, with 6.6.x you could consider editing in flops settings for the apps, making 6.03 slightly higher than 5.28. That seems like it should correct the situation. MarkJ's app_info for AP503, AP505, MB603 and MB608 thread should provide enough detail if you decide to try that.
                                                                                    Joe

Richard Haselgrove:

--- Quote from: Josef W. Segur on 28 Oct 2009, 02:21:34 pm ---
The primary server-side change is that the Scheduler now tells the client to use what it considers the "best" app version. What it considers "best" doesn't consider the version number. Instead it just takes the suitable app versions in order, and chooses the one with the highest flops rating. If the flops are equal, the first suitable app is considered "best".


--- End quote ---

I wonder whether that explains the tendency for SETI to fill the CUDA cache before the CPU cache, in times of drought.

(Assuming your CUDA card is faster than your CPU, that is.)

Franz:

--- Quote from: Josef W. Segur on 28 Oct 2009, 02:21:34 pm ---Franz, with 6.6.x you could consider editing in flops settings for the apps, making 6.03 slightly higher than 5.28. That seems like it should correct the situation. MarkJ's app_info for AP503, AP505, MB603 and MB608 thread should provide enough detail if you decide to try that.
                                                                                    Joe

--- End quote ---
mmmmmm mumbe mumble ... I don't like to change app_info ... but If I have to do it, I think that the better solution is to delete the 528 section .... isn't it?

So...

<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>

What do you think?

Franz

Josef W. Segur:

--- Quote from: Franz on 29 Oct 2009, 01:49:43 pm ---mmmmmm mumbe mumble ... I don't like to change app_info ... but If I have to do it, I think that the better solution is to delete the 528 section .... isn't it?

So...

<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>

What do you think?

Franz
--- End quote ---

Finish and report any already downloaded work which has been already assigned to 5.28 first, or BOINC will trash it. Other users might be grateful to get the reissues, but with the project having very little new work to deliver your host might be idle for awhile.
                                                                         Joe

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version