Skip to content

Conversation

@shrinath-suresh
Copy link
Collaborator

@shrinath-suresh shrinath-suresh commented Nov 22, 2022

Signed-off-by: Shrinath Suresh [email protected]

What changes are proposed in this pull request?

MLflow 2.0 compatibility with latest PT and PTL

How is this patch tested?

Titanic

Screenshot from 2022-12-15 08-25-58
Screenshot from 2022-12-15 08-26-42
Screenshot from 2022-12-15 08-27-19
titanic_training.txt

Iris Classification

iris_training.txt
iris_training_gpu.txt
Screenshot from 2022-12-15 09-51-51
Screenshot from 2022-12-15 09-52-08
Screenshot from 2022-12-15 09-52-27

Screenshot from 2022-12-15 09-52-44

IrisClassification - Torchscripted

iris_torchscript_training.txt
Screenshot from 2022-12-15 10-01-34
Screenshot from 2022-12-15 10-01-49
Screenshot from 2022-12-15 10-02-17

MNIST

mnist_training.txt
mnist_training_gpu.txt
Screenshot from 2022-12-15 10-16-03
Screenshot from 2022-12-15 10-16-22

CIFAR

cifar_training.txt
cifar_training_gpu.txt
Screenshot from 2022-12-15 10-32-13
Screenshot from 2022-12-15 10-33-48

Release Notes

Is this a user-facing change?

  • No. You can skip the rest of this section.
  • Yes. Give a description of this change to be included in the release notes for MLflow TorchServe Deployment Plugin users.

(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)

What component(s) does this PR affect?

Components

  • area/deploy: Main deployment plugin logic
  • area/build: Build and test infrastructure for MLflow TorchServe Deployment Plugin
  • area/docs: MLflow TorchServe Deployment Plugin documentation pages
  • area/examples: Example code

How should the PR be classified in the release notes? Choose one:

  • rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
  • rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
  • rn/feature - A new user-facing feature worth mentioning in the release notes
  • rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
  • rn/documentation - A user-facing documentation change worth mentioning in the release notes

Signed-off-by: Shrinath Suresh <[email protected]>
Signed-off-by: Shrinath Suresh <[email protected]>
Signed-off-by: Shrinath Suresh <[email protected]>
…into mlflow-2.0-compatibility

Signed-off-by: Shrinath Suresh <[email protected]>
Signed-off-by: Shrinath Suresh <[email protected]>
Signed-off-by: Shrinath Suresh <[email protected]>
Signed-off-by: Shrinath Suresh <[email protected]>
@shrinath-suresh shrinath-suresh changed the title [WIP] mlflow 2.0 compatibility mlflow 2.0 compatibility Dec 15, 2022
self.train_acc = Accuracy()
self.val_acc = Accuracy()
self.test_acc = Accuracy()
self.train_acc = Accuracy(task="multiclass", num_classes=3)
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Latest torchmetrics expects task and num_classes to be passed while using Accuracy - https://torchmetrics.readthedocs.io/en/stable/classification/accuracy.html

_DEFAULT_TORCHSERVE_LOCAL_MANAGEMENT_PORT = "8081"


class CustomPredictionsResponse(PredictionsResponse):

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Do we want to call this TorchServePredictionsResponse?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dbczumar I have done this change as a separate PR. Can you please review it when you find time. The builds are passing.

Copy link

@dbczumar dbczumar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks @shrinath-suresh !

@GeeCastro
Copy link

Hi, are you still considering this PR?

@shrinath-suresh
Copy link
Collaborator Author

@chauhang Can you please review and approve the PR so that we can merge ?

@chauhang chauhang merged commit a442b98 into master Feb 12, 2023
@chauhang chauhang deleted the mlflow-2.0-compatibility branch February 12, 2023 20:41
@shrinath-suresh
Copy link
Collaborator Author

Thanks @chauhang and @dbczumar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants