@proceedings {496,
	title = {Spotnik: Designing Distributed Machine Learning for Transient Cloud Resources},
	journal = {12th USENIX Workshop on Hot Topics in Cloud Computing (HotCloud)},
	year = {2020},
	month = {07/2020},
	publisher = {USENIX},
	address = {Boston, MA, USA},
	abstract = {To achieve higher utilisation, cloud providers offer VMs with GPUs as lower-cost transient cloud resources. Transient VMs can be revoked at short notice and vary in their avail- ability. This poses challenges to distributed machine learning (ML) jobs, which perform long-running stateful computation in which many workers maintain and synchronise model replicas. With transient VMs, existing systems either require a fixed number of reserved VMs or degrade performance when recovering from revoked transient VMs. We believe that future distributed ML systems must be designed from the ground up for transient cloud resources. This paper describes SPOTNIK, a system for training ML models that features a more adaptive design to accommodate transient VMs: (i) SPOTNIK uses an adaptive implementation of the all-reduce collective communication operation. As workers on transient VMs are revoked, SPOTNIK updates its membership and uses the all-reduce ring to recover; and (ii) SPOTNIK supports the adaptation of the synchronisation strategy between workers. This allows a training job to switch between different strategies in response to the revocation of transient VMs. Our experiments show that, after VM revocation, SPOTNIK recovers training within 300 ms for ResNet/ImageNet.},
	author = {Marcel Wagenl{\"a}nder and Luo Mai and Guo Li and Peter Pietzuch}
}
