Changes between Version 12 and Version 13 of assign+


Ignore:
Timestamp:
Aug 7, 2013 12:45:08 PM (7 years ago)
Author:
sunshine
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • assign+

    v12 v13  
    5959
    6060||Category|| Count|| Percentage || Reason ||
    61 || Both ''assign'' and ''assign+'' succeeded || 98,589 || 90% || n/a ||
    62 || ''assign'' succeeded, ''assign+'' failed || 150 || 0.1% || ||
     61|| Both ''assign'' and ''assign+'' succeeded || 98,639 || 90% || n/a ||
     62|| ''assign'' succeeded, ''assign+'' failed || 98 || 0.1% || In 93 of these cases ''assign'' doesn't detect a disconnected switch topology nor oversubscribed interswitch bandwidth, but it should. In 2 cases we overestimate what we need in one vclass. I can fix this issue but it will have to wait. In 3 cases the ''ptopfile'' has an error - two interfaces on a physical node are called the same. ''assign'' doesn't pick up on this but ''assign+'' does, which should be correct behavior. So effectively in only 2 out of 109,326 ''assign'' is better than ''assign+''. ||
    6363||  Both ''assign'' and ''assign+'' failed || 6,341 || 5.8% || ||
    6464|| ''assign'' failed, ''assign+'' succeeded, ''assign'' succeeded with fixed nodes from ''assign+'' || 666 || 0.6% || ||
    65 || ''assign'' failed, ''assign+'' succeeded, ''assign'' failed with fixed nodes from ''assign+'' || 3,580 || 3.2% || ||
     65|| ''assign'' failed, ''assign+'' succeeded, ''assign'' failed with fixed nodes from ''assign+'' || 3,580 || 3.2% || This happens because ''assign'' cannot properly deal with fixed interfaces. I checked quite a few of these solutions manually and they are possible solutions. ||