next up previous contents
Next: Empirically Up: Performance Previous: Performance

Theoretically

The Branch and Bound algorithm's worst case runtime is bound by tex2html_wrap_inline130 , where n is the number of tasks. The worst case only happens on an input instance where every node of the schedule tree needs to be examined, or no groups of schedules can be skipped from the upper and lower bound information. The number of partial schedule nodes that would need to be examined in this case would be tex2html_wrap_inline134 which is in tex2html_wrap_inline136 . The insert and delete functions according to the LEDA manual take time in tex2html_wrap_inline138 , where k is the number of nodes in the heap. The size of the heap will be about tex2html_wrap_inline142 , which implies that insert and delete are tex2html_wrap_inline144 in a measure of the number of tasks. Every node that will be examined will need to be at least deleted from the heap, with tex2html_wrap_inline136 nodes taking time tex2html_wrap_inline148 to delete you get the run time bound by tex2html_wrap_inline130 .


Jamie Marconi
Thu May 23 19:44:07 PDT 1996