TensorFlow Batch Predict

Batch Prediction for TensorFlow models

Kubeflow Batch Predict

Kubeflow batch-predict allows users to run predict jobs over a trained TensorFlow model in SavedModel format in a batch mode. It is apache-beam-based and currently runs with a local runner on a single node in a K8s cluster.

Run a TensorFlow Batch Predict Job

Note: Before running a job, you should have deployed kubeflow to your cluster.

To run batch prediction, we create a Kubernetes job to run beam. Kubeflow provides a ksonnet prototype suitable for you to to generate a component which you can then customize for your jobs.

Create the component


ks registry add kubeflow-git github.com/kubeflow/kubeflow/tree/${VERSION}/kubeflow
ks pkg install kubeflow-git/examples

ks generate tf-batch-predict ${MY_BATCH_PREDICT_JOB}
  --gcpCredentialSecretName=${GCP_CREDENTIAL_SECRET_NAME} \
  --inputFilePatterns=${INPUT_FILE_PATTERNS} \
  --inputFileFormat=${INPUT_FILE_FORMAT} \
  --modelPath=${MODEL_PATH} \
  --outputResultPrefix=${OUTPUT_RESULT_PREFIX} \
  --outputErrorPrefix=${OUTPUT_ERROR_PREFIX} \

The supported parameters and their usage:

  • inputFilePatterns The list of input files or file patterns, separated by commas.

  • inputFileFormat One of the following values: json, tfrecord, and tfrecord_gzip.

  • modelPath The path containing the model files in SavedModel format.

  • batchSize Number of prediction instances in one batch. This largely depends on how many instances can be held and processed simultaneously in the memory of your machine.

  • outputResultPrefix Output path to save the prediction results.

  • outputErrorPrefix Output path to save the prediction errors.

  • numGpus Number of GPUs to use per machine.

  • gcpCredentialSecretName Secret name if used on GCP. Only needed for running the jobs in GKE in order to output results to GCS.

You can set or update values for optional parameters after generating the component. For example, you can set the modelPath to a new value (e.g. to test out another model) or set the output to another gcs location (e.g. in order not to overwrite the results from previous runs). For example:

ks param set --env=default ${MY_BATCH_PREDICT_JOB} modelPath gs://my_new_bucket/my_new_model
ks param set --env=default ${MY_BATCH_PREDICT_JOB} outputResultPrefix gs://my_new_bucket/my_new_output

Use GPUs

To use GPUs your cluster must be configured to use GPUs.

When all the conditions above are satisfied, you should set the number of GPU to a positive integer. For example:

ks param set --env=default ${MY_BATCH_PREDICT_JOB} numGpus 1

This way, the batch-predict job will use a GPU version of docker image and add appropriate configuration to start the kubernetes job.

Submit the job


You should see that a job is started to provision the batch-predict docker image. Then a pod starts to run the job.

kubectl get pods
kubectl logs -f ${POD_NAME}

You can check the state of the pod to determine if a job is running, failed, or completed. Once it is completed, you can check the result output location to see if any sensible results are generated. If anything goes wrong, check the error output location where the error message is stored.

Delete the job