Quote Originally Posted by somanyroads View Post
This thread is about GPU tasks, but 7.0.42 and app_config.xml certainly help control the number of running cpu tasks also. However, there seems to be no change in the ability of 7.0.42 to get work; still have to manually suspend a cpu task or two to download cpu work on another task even though a core is sitting idle. Even Project Updater won't get work for the cpu task that has no work until some other cpu task is suspended. If left alone, will 7.0.42 "learn" to get work for all running tasks?
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. When it comes to BOINC features that get added, it is often the tail wagging the dog. One project wants a change and all others suffer because of it. So, rather than require the project admins to use realistic estimates on the flops for a WU, they decided to make the BOINC client smarter which, as is often the case, created a slew of problems that will be around for a number of versions. 7.0.33 seems to get work OK but 7.0.38 and later have a variety of problems. About the time the get to X.X.50 or higher, they get the kinks worked out. Then they start on a new major release and it starts all over again.