Spatial Sharing of GPU for Autotuning DNN models

Abstract

GPUs are used for training, inference, and tuning the machine learning models. However, Deep Neural Network (DNN) models vary widely in their ability to exploit the full power of high-performance GPUs. Spatial sharing of GPU enables multiplexing several applications on the GPU and can improve utilization of the GPU, thus improving throughput and lowering latency. DNN models given just the right amount of GPU resources can still provide low inference latency, just as much as dedicating all of the GPU for their inference task. An approach to improve DNN inference performance is hardware-specific tuning of the DNN model. Autotuning frameworks find the optimal low-level implementation for a certain target device based on the trained machine learning model, thus reducing the DNN's inference latency and increasing inference throughput. We observe an inter-dependency between the tuned model and its inference latency. A DNN model tuned with specific GPU resources provides the best inference latency when inferred with close to the same amount of GPU resources. However, a model tuned with the maximum amount of the GPU's resources has poorer inference latency once the GPU resources are limited for inference. On the other hand, a model tuned with an appropriate amount of GPU resources still achieves good inference latency across a wide range of GPU resource availability. We explore the underlying causes that impact the tuning of a model at different amounts of GPU resources. We present a number of techniques to maximize resource utilization and improve tuning performance. We enable controlled spatial sharing of GPU to multiplex several tuning applications on the GPU. We scale the tuning server instances and shard the tuning model across multiple client instances for concurrent tuning of different operators of a model, achieving better GPU multiplexing. With our improvements, we decrease DNN autotuning time by upto 75% and increase throughput by a factor of 5.Preprint. Under review.

A Survey of Multi-Tenant Deep Learning Inference on GPU

“…Such assumption and the single-tenant targeted configuration however becomes unsuitable for concurrent multi-kernel execution since each kernel only has partial resource available. According to [9], the maximum throughput gap comparing single-tenant vs. multi-tenant tuned configurations for the same computing kernel could reach 5× difference.…”

“…However, as multi-tenant DNNs share the underlying resource, kernels optimized for single-tenant settings can easily become sub-optimal for multitenant scenarios. Recently, there are certain works that show multi-tenant DL computing should optimize kernel configurations according to its available resource ratio during practical execution [9], which shows a 5× throughput difference. 5 Resource-level: To achieve adaptive multi-tenant resource partitioning and provisioning, it asks for both strategic design and hardware support.…”