REST API inference in PyTorch - Model Pipeline Trace

Model Pipeline - REST API inference

This pipeline shows how a trained PyTorch model receives data through a REST API, processes it, and returns predictions. It covers data input, preprocessing, model inference, and output formatting.

Data Flow - 5 Stages

1API receives JSON input

1 request with JSON payload→Receive raw JSON data from client→1 JSON object with feature values

{"feature1": 5.1, "feature2": 3.5, "feature3": 1.4, "feature4": 0.2}

↓

2Preprocessing

1 JSON object with 4 features→Convert JSON to PyTorch tensor and normalize features→1 tensor of shape (1, 4)

[[0.5, 0.7, 0.2, 0.1]]

↓

3Model inference

1 tensor of shape (1, 4)→Feed tensor into trained PyTorch model to get raw output→1 tensor of shape (1, 3)

[[2.1, 0.3, -1.2]]

↓

4Postprocessing

1 tensor of shape (1, 3)→Apply softmax to get class probabilities→1 tensor of shape (1, 3) with probabilities

[[0.84, 0.10, 0.06]]

↓

5API sends JSON response

1 tensor of shape (1, 3) with probabilities→Convert probabilities to JSON format and send back→1 JSON object with class probabilities

{"class_0": 0.84, "class_1": 0.10, "class_2": 0.06}

Training Trace - Epoch by Epoch

Loss
1.2 |****
1.0 |***
0.8 |**
0.6 |**
0.4 |*
0.2 |
    +----------------
     1 2 3 4 5 Epochs

Epoch	Loss ↓	Accuracy ↑	Observation
1	1.20	0.45	Model starts learning with high loss and low accuracy
2	0.85	0.65	Loss decreases and accuracy improves
3	0.60	0.78	Model continues to improve
4	0.45	0.85	Good convergence with lower loss and higher accuracy
5	0.35	0.90	Training stabilizes with strong performance

Prediction Trace - 5 Layers

Layer 1: Receive JSON input

Layer 2: Preprocessing

Layer 3: Model forward pass

Layer 4: Softmax activation

Layer 5: Format JSON response

Model Quiz - 3 Questions

What shape does the data have after preprocessing before model input?

A 1 tensor of shape (1, 4)

B 1 JSON object with 4 features

C 1 tensor of shape (4, 1)

D 1 tensor of shape (1, 3)

Key Insight

This visualization shows how a trained PyTorch model can be wrapped in a REST API to receive input data, preprocess it, run inference, and return predictions as probabilities. The training trace confirms the model learns well, and the prediction trace explains how raw input transforms step-by-step to output probabilities.

Practice

1. What is the main purpose of using a REST API for PyTorch model inference?

easy

A. To train the model faster using multiple GPUs

B. To send data to the model and receive predictions over the web

C. To visualize the model architecture in a browser

D. To save the model weights to disk

Solution

1. Step 1: Understand REST API role

   A REST API allows communication over the web by sending requests and receiving responses.

2. Step 2: Connect REST API with model inference

   In PyTorch, a REST API is used to send input data and get predictions from the model remotely.

3. Final Answer:

   To send data to the model and receive predictions over the web -> Option B

4. Quick Check:

   REST API = Web data exchange for predictions [OK]

Hint: REST API = send input, get prediction over web [OK]

Common Mistakes:

• Confusing inference with training
• Thinking REST API is for saving models
• Assuming REST API visualizes models

2. Which of the following is the correct way to disable gradient calculation during inference in a Flask REST API using PyTorch?

easy

A. with torch.no_grad():

B. model.train()

C. torch.enable_grad()

D. model.backward()

Solution

1. Step 1: Identify how to disable gradients

   PyTorch uses torch.no_grad() context to turn off gradient tracking during inference.

2. Step 2: Check other options

   model.train() enables training mode, torch.enable_grad() enables gradients, and model.backward() is invalid.

3. Final Answer:

   with torch.no_grad(): -> Option A

4. Quick Check:

   Disable gradients = torch.no_grad() [OK]

Hint: Use torch.no_grad() to save memory during inference [OK]

Common Mistakes:

• Using model.train() instead of model.eval()
• Not disabling gradients causing slow inference
• Calling backward() during inference

3. Given this Flask route for inference, what will be the output if the input JSON is {'input': [1.0, 2.0]} and the model returns tensor([3.0])?

from flask import Flask, request, jsonify
import torch
app = Flask(__name__)
model = torch.nn.Linear(2, 1)
model.eval()

@app.route('/predict', methods=['POST'])
def predict():
    data = request.get_json()
    x = torch.tensor(data['input']).unsqueeze(0).float()
    with torch.no_grad():
        output = model(x)
    return jsonify({'prediction': output.item()})

medium

A. {"prediction": "tensor([3.0])"}

B. {"prediction": [3.0]}

C. Error: model not loaded

D. {"prediction": 3.0}

Solution

1. Step 1: Understand input and output processing

   The input JSON is converted to a tensor with shape (1, 2). The model outputs a tensor with shape (1, 1).

2. Step 2: Check output conversion

   The output tensor's single value is extracted using output.item(), which returns a float, then wrapped in JSON.

3. Final Answer:

   {"prediction": 3.0} -> Option D

4. Quick Check:

   output.item() returns float for JSON [OK]

Hint: Use output.item() to get scalar from tensor for JSON [OK]

Common Mistakes:

• Returning tensor object directly in JSON
• Forgetting to convert input to tensor
• Not using torch.no_grad() causing slow inference

4. You wrote this Flask REST API code for inference but get an error: 'RuntimeError: expected scalar type Float but found Double'. What is the likely fix?

@app.route('/predict', methods=['POST'])
def predict():
    data = request.get_json()
    x = torch.tensor(data['input'])
    with torch.no_grad():
        output = model(x)
    return jsonify({'prediction': output.item()})

medium

A. Convert input tensor to float using .float() before passing to model

B. Call model.train() before inference

C. Remove torch.no_grad() context

D. Change model output to int

Solution

1. Step 1: Understand the error cause

   The model expects float tensors but input tensor is double (default from Python floats).

2. Step 2: Fix input tensor type

   Convert input tensor to float type using .float() before passing to the model.

3. Final Answer:

   Convert input tensor to float using .float() before passing to model -> Option A

4. Quick Check:

   Tensor dtype mismatch fixed by .float() [OK]

Hint: Always convert input to float tensor before model call [OK]

Common Mistakes:

• Not converting input data type
• Calling model.train() during inference
• Removing torch.no_grad() causing slow inference

5. You want to deploy a PyTorch model as a REST API that accepts images, preprocesses them, and returns class predictions. Which sequence of steps is best practice inside your Flask route?

hard

A. Load model globally, call model.eval(), preprocess input image to numpy array, call model backward(), return JSON

B. Load model inside route on every request, call model.train(), preprocess input, get prediction, return JSON

C. Load model once globally, set model.eval(), preprocess input image to tensor, use torch.no_grad(), get prediction, return JSON

D. Preprocess input image after prediction, load model globally, call torch.enable_grad(), return raw tensor

Solution

1. Step 1: Model loading and mode

   Load the model once globally to avoid overhead and set it to evaluation mode with model.eval().

2. Step 2: Input preprocessing and inference

   Preprocess the input image to a tensor, use torch.no_grad() to disable gradients, get prediction, and return JSON response.

3. Final Answer:

   Load model once globally, set model.eval(), preprocess input image to tensor, use torch.no_grad(), get prediction, return JSON -> Option C

4. Quick Check:

   Efficient inference = global load + eval + no_grad + preprocess [OK]

Hint: Load model once, eval mode, no_grad, preprocess input tensor [OK]

Common Mistakes:

• Loading model on every request causing slow response
• Using model.train() during inference
• Not preprocessing input to tensor
• Calling backward() during inference