Quote Originally Posted by Slicker View Post
Maybe. Maybe not. I've had projects sit idle for days even with all other projects suspended. When they got rid of short and long term debts and replaced them with fancier algorithms, BOINC got worse -- as usual.
Does anyone know if it is the intent of BOINC to allow "<max_concurrent>N</max_concurrent>" in app_config.xml to override the default settings to fetch work? A project like Neurona that runs one task at a time and is 1-out-1-in doesn’t stand a chance of getting tasks especially if the other cpu tasks keep changing and their caches are always full. Moving to Numberfields@home for a short challenge seems to have upset BOINC and it cannot remember what it was doing the day before.