TensorSocket: Shared Data Loading for Deep Learning Training
Not on the map. Why?
Abstract (arXiv)
Training deep learning models is a repetitive and resource-intensive process. Data scientists often train several models before landing on a set of parameters (e.g., hyper-parameter tuning) and model architecture (e.g., neural architecture search), among other things that yield the highest accuracy. The computational efficiency of these training tasks depends highly on how well the training data is supplied to the training process. The repetitive nature of these tasks results in the same data processing pipelines running over and over, exacerbating the need for and costs of computational resources. In this paper, we present TensorSocket to reduce the computational needs of deep learning training by enabling simultaneous training processes to share the same data loader. TensorSocket mitigates CPU-side bottlenecks in cases where the collocated training workloads have high throughput on GPU, but are held back by lower data-loading throughput on CPU. TensorSocket achieves this by reducing redundant computations and data duplication across collocated training processes and leveraging modern GPU-GPU interconnects. While doing so, TensorSocket is able to train and balance differently-sized models and serve multiple batch sizes simultaneously and is hardware- and pipeline-agnostic in nature. Our evaluation shows that TensorSocket enables scenarios that are infeasible without data sharing, increases training throughput by up to 100%, and when utilizing cloud instances, achieves cost savings of 50% by reducing the hardware resource needs on the CPU side. Furthermore, TensorSocket outperforms the state-of-the-art solutions for shared data loading such as CoorDL and Joader; it is easier to deploy and maintain and either achieves higher or matches their throughput while requiring fewer CPU resources.
Key facts. Cited by 3 papers in the map (data through 7 Oct 2026). Builds on 22 of its 65 references that are in the map. First posted on arXiv 27 Sep 2024.
Builds on
22 of 65 references.
References · 22
- 2019PyTorch: An Imperative Style, High-Performance Deep Learning Librarycited by 20,160
- 2022Hierarchical Text-Conditional Image Generation with CLIP Latentscited by 6,539
- 2019Energy and Policy Considerations for Deep Learning in NLPcited by 1,242
- 2019Green AIcited by 620
- 2017Progressive Neural Architecture Searchcited by 483
- 2018A System for Massively Parallel Hyperparameter Tuningcited by 201
- 2022The Carbon Footprint of Machine Learning Training Will Plateau, Then Shrinkcited by 183
- 2020Carbontracker: Tracking and Predicting the Carbon Footprint of Training Deep Learning Modelscited by 168
- 2022Measuring the Carbon Intensity of AI in Cloud Instancescited by 110
- 2018Tunability: Importance of Hyperparameters of Machine Learning Algorithmscited by 98
- 2019Analysis of Large-Scale Multi-Tenant GPU Clusters for DNN Training Workloadscited by 79
- 2021tf.data: A Machine Learning Data Processing Frameworkcited by 40
10 more
- 2020Analyzing and Mitigating Data Stalls in DNN Trainingcited by 35
- 2024Hype, Sustainability, and the Price of the Bigger-is-Better Paradigm in AIcited by 35
- 2021Understanding Data Storage and Ingestion for Large-Scale Deep Recommendation Model Trainingcited by 28
- 2021Plumber: Diagnosing and Removing Performance Bottlenecks in Machine Learning Data Pipelinescited by 15
- 2022tf.data service: A Case for Disaggregating ML Input Data Processingcited by 15
- 2019CROSSBOW: Scaling Deep Learning with Small Batch Sizes on Multi-GPU Serverscited by 14
- 2022Where Is My Training Bottleneck? Hidden Trade-Offs in Deep Learning Preprocessing Pipelinescited by 10
- 2021Horizontally Fused Training Array: An Effective Hardware Utilization Squeezer for Training Novel Deep Learning Modelscited by 7
- 2022An Analysis of Collocation on GPUs for Deep Learning Trainingcited by 6
- 2020Training for Speech Recognition on Coprocessorscited by 2
Built on by
Citing papers per year: 2025: 2; 2026: 1.
3 papers.