RICH: Strategy-proof and efficient coflow scheduling in non-cooperative environments

Coflow scheduling can effectively improve the application performance and has been studied a lot in cooperative environments (e.g., private datacenter networks), where fairness is not the primary concern. In non-cooperative environments (e.g., multi-tenant datacenter networks), coflow scheduling should be strategy-proof; otherwise, some tenants could unfairly acquire more resources by cheating the scheduler. As minimizing coflow completion time (CCT) must prioritize coflows based on some specific rules (e.g., shortest-coflow-first, smallest-effective-bottleneck-first), tenants can raise the priority of their coflows by lying about the coflow information. Thus, it is a common belief that optimizing coflow performance can inevitably violate strategy-proofness.