Response to Geeta's first posting above:
If you only have 40 workloads, then it really doesn't matter from the performance perspective if you re-order the evaluation order list based on workoads with the most hits going first. The primary reason for ordering the evaulation order to is in the case where the ordering is essential for correct classification, such as when you have workloads such as this:
MSI-Short: Account = ‘$M1$MSI&I’, Est Time <= 20 Sec. (High priority)
MSI-Medium: Account = ‘$M1$MSI&I’, Est Time <= 500 Sec. (Medium priority)
MSI-Long: Account = ‘$M1$MSI&I’, Est Time <= 2000 Sec. (Low priority)
If you have MSI-Long higher in the evaluation order than MSI-Medium or MSI-Short, all MSI queries will classify there. So even if MSI-Long was a more popular classification destination, it would be a mistake to put it higher in the evaluation order.
Thanks, -Carrie
Response to Geeta's first posting above:
If you only have 40 workloads, then it really doesn't matter from the performance perspective if you re-order the evaluation order list based on workoads with the most hits going first. The primary reason for ordering the evaulation order to is in the case where the ordering is essential for correct classification, such as when you have workloads such as this:
MSI-Short: Account = ‘$M1$MSI&I’, Est Time <= 20 Sec. (High priority)
MSI-Medium: Account = ‘$M1$MSI&I’, Est Time <= 500 Sec. (Medium priority)
MSI-Long: Account = ‘$M1$MSI&I’, Est Time <= 2000 Sec. (Low priority)
If you have MSI-Long higher in the evaluation order than MSI-Medium or MSI-Short, all MSI queries will classify there. So even if MSI-Long was a more popular classification destination, it would be a mistake to put it higher in the evaluation order.
Thanks, -Carrie