According to SageMaker batch transform facts, initializing multiple compute instances with only one input file results in only one active instance while the rest are idle. To partition the file into mini-batches and utilize the instances, SplitType must be set to Line. The MaxPayloadInMB cannot exceed 100 MB, and output filenames are automatically appended with .out upon successful processing.
In SageMaker batch transform, the MaxPayloadInMB parameter must not exceed 100 MB. If MaxConcurrentTransforms is set, the product of the two parameters must not exceed 100 MB. On successful execution, the output file retains the same name as the input file, with .out appended.
According to the facts, Amazon SageMaker batch transform is the correct feature to use when you need to preprocess datasets to remove noise or bias, get inferences from large datasets, run inference without a persistent endpoint, and associate input records with inferences to help with results interpretation.
When a batch transform job starts, SageMaker AI partitions the Amazon S3 objects in the input by key and maps those S3 objects to instances. If multiple compute instances are initialized but only a single input file exists, only one instance will process the file, leaving the other instances idle.
In SageMaker batch transform, mini-batch size is controlled using BatchStrategy and MaxPayloadInMB. MaxPayloadInMB cannot exceed 100 MB, and if MaxConcurrentTransforms is set, the product of MaxConcurrentTransforms and MaxPayloadInMB must not exceed 100 MB.
A machine learning developer is configuring an Amazon SageMaker batch transform job. They initialize multiple compute instances to process a single large input file. However, during execution, they notice that only one compute instance is active while the rest remain idle. They need to partition the input file into mini-batches to resolve this. Which configuration or behavior explains this scenario and provides the correct solution?
How confident are you in this answer?