REVIEW 2 cited by
Robust Scheduling with GFlowNets
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
Finding the best way to schedule operations in a computation graph is a classical NP-hard problem which is central to compiler optimization. However, evaluating the goodness of a schedule on the target hardware can be very time-consuming. Traditional approaches as well as previous machine learning ones typically optimize proxy metrics, which are fast to evaluate but can lead to bad schedules when tested on the target hardware. In this work, we propose a new approach to scheduling by sampling proportionally to the proxy metric using a novel GFlowNet method. We introduce a technique to control the trade-off between diversity and goodness of the proposed schedules at inference time and demonstrate empirically that the pure optimization baselines can lead to subpar performance with respect to our approach when tested on a target model. Furthermore, we show that conditioning the GFlowNet on the computation graph enables generalization to unseen scheduling problems for both synthetic and real-world compiler datasets.
Forward citations
Cited by 2 Pith papers
-
A Nurse Staffing and Scheduling Problem with Bounded Flexibility and Demand Uncertainty
A multi-stage stochastic nurse staffing and scheduling model with work-policy bounded flexibility is reduced to a two-stage program and solved with a Generative Flow Network; Tan Tock Seng Hospital experiments show co...
-
A Study of the Efficacy of Generative Flow Networks for Robotics and Machine Fault-Adaptation
On a simulated Reacher arm with four injected faults, CFlowNets matches or beats DDPG, TD3, PPO, and SAC on adaptation speed and asymptotic reward, while using far more GPU memory and wall-clock time.
Discussion (0). Continue with ORCID to comment.