TensorFlow Serving setup - Model Pipeline Trace

Model Pipeline - TensorFlow Serving setup

This pipeline shows how a trained TensorFlow model is prepared and served using TensorFlow Serving. It covers loading the model, preprocessing input data, making predictions, and returning results to users or applications.

Data Flow - 5 Stages

1Model Export

N/A→Save trained TensorFlow model in SavedModel format→SavedModel directory with model files

A trained image classifier saved as /models/my_model/1/

↓

2TensorFlow Serving Load

SavedModel directory→TensorFlow Serving loads the SavedModel for serving→Model ready to receive input requests

Serving loads /models/my_model/1/ into memory

↓

3Input Preprocessing

Batch of raw input data (e.g., images or JSON)→Preprocess inputs to match model input format→Batch of tensors with shape matching model input

Resize and normalize images to 224x224x3 float tensors

↓

4Model Prediction

Batch of preprocessed tensors (e.g., 32 x 224 x 224 x 3)→Run inference using the loaded model→Batch of prediction tensors (e.g., 32 x 10 classes)

Model outputs probabilities for 10 classes per input

↓

5Output Postprocessing

Batch of prediction tensors→Convert model outputs to human-readable labels or scores→Batch of prediction results (e.g., class labels and confidence)

Top predicted class and confidence score per input

Training Trace - Epoch by Epoch

Loss
1.2 |*       
0.9 | **     
0.6 |   ***  
0.3 |     ***
    +--------
     1 2 3 4 5 Epochs

Epoch	Loss ↓	Accuracy ↑	Observation
1	1.2	0.55	Model starts learning with moderate loss and accuracy
2	0.85	0.70	Loss decreases and accuracy improves as model learns
3	0.60	0.80	Model continues to improve with lower loss and higher accuracy
4	0.45	0.85	Training converges with good accuracy and low loss
5	0.40	0.88	Final epoch shows stable loss and high accuracy

Prediction Trace - 3 Layers

Layer 1: Input Preprocessing

Layer 2: Model Inference

Layer 3: Output Postprocessing

Model Quiz - 3 Questions

What is the purpose of the SavedModel format in TensorFlow Serving?

A To visualize training loss and accuracy

B To preprocess input data before prediction

C To store the trained model so TensorFlow Serving can load it

D To postprocess model outputs into labels

Key Insight

TensorFlow Serving allows you to deploy trained models efficiently by loading SavedModel format models and serving predictions in real time. The pipeline ensures input data is properly preprocessed, the model runs inference, and outputs are postprocessed for easy use. Monitoring training loss and accuracy helps confirm the model is ready for serving.

Practice

1. What is the main purpose of TensorFlow Serving in a machine learning workflow?

easy

A. To visualize training data and model metrics

B. To train new machine learning models from scratch

C. To preprocess data before training

D. To deploy trained models for real-time predictions

Solution

1. Step 1: Understand TensorFlow Serving's role

   TensorFlow Serving is designed to make trained models available for real-time use without retraining.

2. Step 2: Differentiate from other tasks

   Training, visualization, and preprocessing are separate steps not handled by TensorFlow Serving.

3. Final Answer:

   To deploy trained models for real-time predictions -> Option D

4. Quick Check:

   Serving = deploy models [OK]

Hint: Serving means making models ready for prediction [OK]

Common Mistakes:

• Confusing serving with training
• Thinking it handles data preprocessing
• Assuming it visualizes metrics

2. Which command correctly starts TensorFlow Serving to serve a model saved in the directory /models/my_model/1/ with model name my_model?

easy

A. tensorflow_model_server --model_name my_model --model_base_path /models/my_model/1/

B. tensorflow_model_server --model_name=my_model --model_path=/models/my_model/1/

C. tensorflow_model_server --model_name=my_model --model_base_path=/models/my_model/1/

D. tensorflow_serve --model_name=my_model --model_base_path=/models/my_model/1/

Solution

1. Step 1: Identify correct flags for TensorFlow Serving

   The correct flags are --model_name and --model_base_path with equal signs.

2. Step 2: Check command correctness

   tensorflow_model_server --model_name=my_model --model_base_path=/models/my_model/1/ uses correct command and flags with equal signs; others have syntax errors or wrong command name.

3. Final Answer:

   tensorflow_model_server --model_name=my_model --model_base_path=/models/my_model/1/ -> Option C

4. Quick Check:

   Correct flags and command = tensorflow_model_server --model_name=my_model --model_base_path=/models/my_model/1/ [OK]

Hint: Use equal signs with flags and correct command name [OK]

Common Mistakes:

• Using spaces instead of equal signs in flags
• Wrong command name like tensorflow_serve
• Using incorrect flag names like --model_path

3. Given the following Python code snippet to send data to a TensorFlow Serving REST API, what will be the printed output if the server returns a prediction of 0.85?

import requests
import json

url = 'http://localhost:8501/v1/models/my_model:predict'
data = {"instances": [[1.0, 2.0, 3.0]]}
response = requests.post(url, json=data)
prediction = response.json()['predictions'][0]
print(prediction)

medium

A. 0.85

B. [0.85]

C. {'predictions': [0.85]}

D. Error: KeyError

Solution

1. Step 1: Understand the response JSON structure

   The server returns a JSON with key 'predictions' holding a list of prediction values, e.g., {'predictions': [0.85]}.

2. Step 2: Extract the first prediction value

   Accessing response.json()['predictions'][0] extracts the float 0.85.

3. Final Answer:

   0.85 -> Option A

4. Quick Check:

   Extract first prediction value = 0.85 [OK]

Hint: Access ['predictions'][0] to get single prediction value [OK]

Common Mistakes:

• Printing the whole JSON instead of the value
• Forgetting to index the first prediction
• Assuming prediction is a list, not a float

4. You tried to start TensorFlow Serving with the command tensorflow_model_server --model_name=my_model --model_base_path=/models/my_model/1/ but got an error saying the model path does not exist. What is the most likely cause?

medium

A. The command should use --model_path instead of --model_base_path

B. The model directory path is incorrect or missing the version subfolder

C. TensorFlow Serving requires the model to be in a .pb file, not a folder

D. The model name must be the full path, not just a name

Solution

1. Step 1: Check model directory structure requirements

   TensorFlow Serving expects model_base_path to point to a directory containing version subfolders like '1', '2', etc.

2. Step 2: Identify common path mistakes

   If the path misses the version folder or is incorrect, the server cannot find the model and throws an error.

3. Final Answer:

   The model directory path is incorrect or missing the version subfolder -> Option B

4. Quick Check:

   Model path must include version folder [OK]

Hint: Model path must include version folder like /1/ [OK]

Common Mistakes:

• Using --model_path instead of --model_base_path
• Pointing to a file instead of a directory
• Confusing model name with path

5. You want to update your TensorFlow model served by TensorFlow Serving without downtime. Which approach allows you to serve the new model version while keeping the old version available for requests?

hard

A. Add the new model version in a new subfolder and update the model config file

B. Stop TensorFlow Serving, replace the old model folder, then restart the server

C. Serve the new model on a different port and manually switch clients

D. Retrain the model inside TensorFlow Serving using the new data

Solution

1. Step 1: Understand TensorFlow Serving versioning

   TensorFlow Serving supports multiple model versions by placing each version in its own numbered subfolder.

2. Step 2: Use model config file to add new version

   Adding the new version folder and updating the config allows serving both versions simultaneously without downtime.

3. Final Answer:

   Add the new model version in a new subfolder and update the model config file -> Option A

4. Quick Check:

   Versioned folders + config update = zero downtime [OK]

Hint: Use versioned folders and config to update without downtime [OK]

Common Mistakes:

• Replacing model folder while server runs
• Restarting server causes downtime
• Trying to retrain model inside serving