SageMaker Pipe Mode
Does SageMaker pipe mode serve as a cost saving measure? Or is is just faster than file mode but generally not much cheaper? The cost savings of it might be 1. no need to copy data to training instances and 2. training instances need less space. Are these savings generally significant for customers?
- 최신
- 최다 투표
- 가장 많은 댓글
To the best of my understanding, pipe mode decreases startup times, but frequently increases the bill.
The SageMaker billing starts after the data has been copied onto the container in File mode and control is transferred to the user script.
Reading the data in pipe mode starts after control is transferred, so the data transfer happens during the billable time.
Further the data is, to the best of my knowledge, not hitting the disk (EBS). This is fast, but also means that if you pass over your data multiple times, you have to re-read it again, on your dime (S3 requests and container wait times).
Pipe mode is still a good idea. For example if you have only few passes over the data and the data is rather large, so that it would not fit on an EBS volume.
Also, in PyTorch for example, data loading can happen in parallel. So while the GPU is chucking away on one batch, the CPUs load and prepare the data for the next batch.
