TorchServe setup in PyTorch - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the TorchServe handler module.

PyTorch

from ts.torch_handler import [1]

Drag options to blanks, or click blank then click option'

Abase_handler

Btorchserve

Cmodel_handler

Dserve

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to import torchserve or serve which are not modules in ts.torch_handler.

Using model_handler which is not a standard import.

The base_handler module is imported from ts.torch_handler to create custom handlers in TorchServe.

2fill in blank

medium

Complete the command to start TorchServe with a model store directory.

PyTorch

torchserve --start --model-store [1] --models my_model.mar

Drag options to blanks, or click blank then click option'

A/tmp/model_store

B/models

C/home/user/models

D/var/model

Attempts:

3 left

💡 Hint

Common Mistakes

Using a directory that does not exist or is not accessible.

Omitting the --model-store option.

The model store directory is specified with --model-store. /tmp/model_store is a common default directory.

3fill in blank

hard

Fix the error in the handler class definition by completing the base class name.

PyTorch

class MyHandler([1]):
    def __init__(self):
        super().__init__()

Drag options to blanks, or click blank then click option'

AHandlerBase

BBaseHandler

CTorchHandler

DModelHandler

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect base class names like HandlerBase or TorchHandler.

Forgetting to call super().__init__() in the constructor.

Custom handlers inherit from BaseHandler class provided by TorchServe.

4fill in blank

hard

Fill both blanks to create a dictionary mapping model names to their .mar files for TorchServe registration.

PyTorch

models = [1]: '[2].mar' for [1] in ['resnet18', 'bert']}

Drag options to blanks, or click blank then click option'

Amodel_name

Bmodel

Cresnet18

Dbert

Attempts:

3 left

💡 Hint

Common Mistakes

Using fixed strings instead of variables in the comprehension.

Mixing variable names between key and value.

The dictionary comprehension uses model_name as the variable and key, and the value is model_name with .mar extension.

5fill in blank

hard

Fill all three blanks to define a TorchServe model archive creation command with model file, handler, and export path.

PyTorch

torch-model-archiver --model-name [1] --version 1.0 --serialized-file [2] --handler [3] --export-path model_store

Drag options to blanks, or click blank then click option'

Aresnet18

Bresnet18.pth

Cimage_classifier

Dbert

Ebert.pth

Ftext_classifier

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing model names and handlers from different model types.

Using incorrect file names or handler names.

The model archive command uses the model name 'resnet18', the serialized file 'resnet18.pth', and the handler 'image_classifier'.

Practice

1. What is the main purpose of TorchServe in PyTorch model deployment?

easy

A. To convert PyTorch models into TensorFlow format

B. To train PyTorch models faster on GPUs

C. To visualize PyTorch model architectures

D. To package and serve PyTorch models for easy deployment

Solution

1. Step 1: Understand TorchServe's role

   TorchServe is designed to help deploy PyTorch models by packaging them and serving predictions.

2. Step 2: Compare options

   Options B, C, and D describe unrelated tasks like training speed, visualization, or conversion, which TorchServe does not do.

3. Final Answer:

   To package and serve PyTorch models for easy deployment -> Option D

4. Quick Check:

   TorchServe = model packaging and serving [OK]

Hint: TorchServe is for deployment, not training or conversion [OK]

Common Mistakes:

• Confusing TorchServe with training tools
• Thinking TorchServe converts model formats
• Assuming TorchServe visualizes models

2. Which command is used to create a model archive (.mar) file for TorchServe?

easy

A. torchserve --start

B. torch-model-archiver

C. python setup.py build

D. torch.save(model, 'model.pth')

Solution

1. Step 1: Identify the command for packaging models

   The torch-model-archiver command creates the .mar file needed by TorchServe.

2. Step 2: Eliminate other commands

   torchserve --start starts the server, python setup.py build is unrelated, and torch.save saves a model but not as a .mar archive.

3. Final Answer:

   torch-model-archiver -> Option B

4. Quick Check:

   Model archive = torch-model-archiver [OK]

Hint: Use torch-model-archiver to package models [OK]

Common Mistakes:

• Using torchserve to create archives
• Confusing torch.save with archiving
• Running unrelated Python build commands

3. Given the following commands, what will be the output after starting TorchServe?

!torch-model-archiver --model-name mymodel --version 1.0 --serialized-file model.pth --handler handler.py --export-path model_store
!torchserve --start --model-store model_store --models mymodel=mymodel-1.0.mar

What happens when you send a prediction request to the server?

medium

A. The server returns predictions from the loaded model

B. The server throws an error because model_store is missing

C. The server starts but does not load any model

D. The server converts the model to ONNX format

Solution

1. Step 1: Understand the archiving and serving commands

   The first command creates a .mar file in model_store. The second starts TorchServe loading that model.

2. Step 2: Predict server behavior on request

   Since the model is loaded, the server will respond with predictions when given input data.

3. Final Answer:

   The server returns predictions from the loaded model -> Option A

4. Quick Check:

   Model archived and loaded = predictions served [OK]

Hint: Archive then start server to serve predictions [OK]

Common Mistakes:

• Assuming model_store folder is missing
• Thinking server starts without loading models
• Believing TorchServe converts model formats

4. You run torchserve --start --model-store model_store --models mymodel=mymodel.mar but get an error: ModelNotFoundError. What is the most likely cause?

medium

A. The handler.py file is missing

B. TorchServe is not installed

C. The .mar file is not in the model_store directory

D. The model name is misspelled in the command

Solution

1. Step 1: Analyze the error message

   ModelNotFoundError means TorchServe cannot find the specified .mar file in the model_store directory.

2. Step 2: Check command and files

   If the .mar file is missing or not placed in model_store, the server cannot load it. Misspelling or missing handler causes different errors.

3. Final Answer:

   The .mar file is not in the model_store directory -> Option C

4. Quick Check:

   ModelNotFoundError = missing .mar file [OK]

Hint: Ensure .mar file is inside model_store folder [OK]

Common Mistakes:

• Ignoring file location for .mar archive
• Assuming TorchServe installation issue
• Confusing model name typo with missing file

5. You want to deploy two different PyTorch models simultaneously using TorchServe. Which setup correctly achieves this?

hard

A. Create two .mar files and start TorchServe with --models model1=model1.mar model2=model2.mar

B. Combine both models into one .mar file and start TorchServe with a single model

C. Start two TorchServe servers on the same port, each serving one model

D. Use torch-model-archiver to merge models into a single .pth file

Solution

1. Step 1: Understand multi-model serving in TorchServe

   TorchServe supports serving multiple models by specifying multiple .mar files with aliases in the --models option.

2. Step 2: Evaluate options

   Create two .mar files and start TorchServe with --models model1=model1.mar model2=model2.mar correctly uses two .mar files with aliases. Combine both models into one .mar file and start TorchServe with a single model is invalid because .mar files cannot combine models. Start two TorchServe servers on the same port, each serving one model fails because two servers cannot share the same port. Use torch-model-archiver to merge models into a single .pth file is incorrect; torch-model-archiver does not merge models.

3. Final Answer:

   Create two .mar files and start TorchServe with --models model1=model1.mar model2=model2.mar -> Option A

4. Quick Check:

   Multiple models = multiple .mar files with aliases [OK]

Hint: Use space-separated model aliases in --models option [OK]

Common Mistakes:

• Trying to merge models into one .mar file
• Running multiple servers on same port
• Misusing torch-model-archiver to combine models