Please, look at this host: http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=39394&offset=0&show_names=0&state=6&appid=
For some reason (maybe recent driver change, maybe some project-side change) server decided that 4k seconds is max time app can spend for task. No matter what reason was (for now), it happened. And BOINC client started to kill one task after another. 4k spent - kill and so on. App making progress in those 4k seconds so such kill is pure waste of host resourses. But even that would be ok, if BOINC could accomodate somehow to new crunching times... but seems it can't! Task aborted with computation error hence its elapsed time doesn't mean anything for BOINC, it just discards it. That is, BOINC will kill tasks on host until all of them will be killed w/o any chance to recover from this situation. I consider this behavior as pure design flaw, some way should be provided for BOINC to accomodate to new crunching times. And even better if whole EXIT_TIME_LIMIT_EXCEEDED behavior will be re-designed. Its primary aim was to prevent endless loops and now it just kills host performance and lead to resourse waste, not save. Any wrong time estimate, especially at new app release and we see lots of such EXIT_TIME_LIMIT_EXCEEDED results killed for nothing. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
