<br><br><div class="gmail_quote">On 24 June 2010 16:24, David Engel <span dir="ltr"><<a href="mailto:david@istwok.net">david@istwok.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Thu, Jun 24, 2010 at 09:50:58AM -0400, Brian J. Murrell wrote:<br>
> I do have Reschedule Higher Priorities disabled in an effort to get<br>
> "best fit" per the other ongoing thread. Changing that either way<br>
> didn't seem to make a difference.<br>
<br>
</div>The scheduler does not use "best fit". It always uses first fit with<br>
some simple heuristics. One of those heuristics is using priority to<br>
control the order in which things are tried.<br>
<div class="im"><br></div></blockquote></div>Hmmm, that misunderstanding maybe my fault. When you said <br><br>"When SchedMoveHigher is enabled, the scheduler moves recordings around one at a time and the first fit wins. it does not continue on looking for "better" fits. Consequently, recordings might get moved to lower priority inputs or channels."<br>
<br>I assumed you meant when SchedMoveHigher is disabled, the scheduler moves recordings around one at
a time looking for a fit and continues looking for
"better" fits until the "best" fit is found.<br><br>Jason<br>