Changes between Version 20 and Version 21 of assign+


Ignore:
Timestamp:
Aug 7, 2013 3:48:52 PM (7 years ago)
Author:
sunshine
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • assign+

    v20 v21  
    7070
    7171||Category|| Count|| Percentage || Reason ||
    72 || Both ''assign'' and ''assign+'' succeeded || 294 || 3% || ''assign'' sometimes fails due to "luck". There is a good solution but it runs out of trials to find it. ||
     72|| Both ''assign'' and ''assign+'' succeeded || 300 || 3% || ''assign'' sometimes fails due to "luck". There is a good solution but it runs out of trials to find it. ||
    7373|| ''assign'' succeeded, ''assign+'' failed || 4 || 0.04% || In one case there was a disconnected switch topology. In other 3 cases ''assign'' does not properly check for OS support and ends up assigning nodes that cannot load a requested OS. Thus effectively there were 0 cases in these tests where ''assign'' was better than ''assign+''. ||
    74 ||  Both ''assign'' and ''assign+'' failed || 9,409 || 95% || n/a ||
    75 || ''assign'' failed, ''assign+'' succeeded, ''assign'' succeeded with fixed nodes from ''assign+'' || 147 || 1.5% || There is a good solution but ''assign'' cannot find it in a given number of trials. ||
     74||  Both ''assign'' and ''assign+'' failed || 9,409 || 95/4% || n/a ||
     75|| ''assign'' failed, ''assign+'' succeeded, ''assign'' succeeded with fixed nodes from ''assign+'' || 147 || 1.49% || There is a good solution but ''assign'' cannot find it in a given number of trials. ||
    7676|| ''assign'' failed, ''assign+'' succeeded, ''assign'' failed with fixed nodes from ''assign+'' || 1 || 0.01% || This happens because ''assign'' cannot properly deal with fixed interfaces. I checked quite a few of these solutions manually and they are possible solutions. ||
    7777