Forum > Windows

Qustion about flops

<< < (2/2)

Josef W. Segur:

--- Quote from: Jim_S on 26 Aug 2010, 03:22:16 pm ---Is there need to change anything if you are only doing CPU crunching with an OPTI APP? :P
--- End quote ---

If you're only doing CPU MB and no Astropulse, the system will work fine. That actually applies to any project where you're using only a single application, the DCF can be reasonably stable without flops. But even doing both MB CPU and Astropulse CPU at S@H is likely to be somewhat problematic. The relative rsc_fpops_est values produced by the splitters were calibrated at SETI Beta before the first release of Astropulse so the combination without flops makes AP estimates high, then for hosts which have done more than 10 MB tasks but fewer than 10 AP tasks the unscaled AP estimates makes the ratio even worse. The long AP estimates inhibit work fetch, a nuisance magnified by 3 day outages.

For those of us using relatively modest hardware, even the AP situation can be handled fairly easily when it arises by editing the AP task's rsc_fpops_est in client_state.xml to make the runtime estimate about right (in effect doing what the servers will do once they have 10 validations averaged). That's the way I intend to deal with it on my Win98SE host, it's running an old BOINC to be compatible with my Win95 host so neither supports flops in an app_version.
                                                                                    Joe

Navigation

[0] Message Index

[*] Previous page