On Apr 24, 2009, at 2:06 PM, Richard Haselgrove wrote: >> And the new "Request CPU reschedule: Idle state change" message. > > I'm not sure quite what's "new" about this. > > As I said, I instinctively took precautions by screen-grabbing > BoincView before touching the v6.6.24 testbed. That's because the BV > machine itself, my P4 Northwood daily driver running BOINC v5.10.13, > also switches tasks when I wake it from idle. I haven't seen the > message before, but then I haven't activated so many debug flags > until needed for this release.
If I read the note right this is a new or improved message. My point is still that we are doing this far too often. If we are already on a 60 second cycle, the only other time it should be needed to run this process is when a resource goes idle. Alternatively if we do this based on so many trigger events, then why do we have to do it every 60 seconds also. Moderation can be a good thing. Again, the point being that we still have the issue were BOINC continually changes its mind about what should be running. One of the causes is that we call the schedulling routine so often. But that is not all of it. Even if we do throttle the number of calls to this routine it will not stop the switching because the deadline rules are still skee-woof, but it will help reduce the onset slightly. _______________________________________________ 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.
