MLops Challenge

Deadline

The deadline for the challenge is June 25th, 2023.

How to participate?

If you are interested in participating in the challenge, please send us an email with the topic MLOps Challenge to challenge-submission@blockshop.org, make sure to add your GitHub email/username and attach your CV.

Description

Create a service that deploys five NLP models for inference, then receives messages through an exposed POST API endpoint, and finally returns inference results (of all five models) in a single response body. Expected deliverable is a service packed in the Docker image.

You service could be a well-configured framework or a self-made API server; use any ML model deployment tool you see fit. There's no language limitation. The most important here is the reusability of a final project.

Challenge flow

Create a dev branch
Submit your solution
Create a PR
Wait for the test results

Requirements

Github

Once you have a collaborator's access to the repository, please create a separate branch for your submission. If you think that your submission is ready, please create a pull request, and assign @rsolovev and @darknessest as reviewers. We will check your submission, run tests and respond with benchmark results and possibly some comments.

Folders Structure

Please work on your solution for the challenge inside the solution folder.

If you need to add env vars to the container, update values in the Helm chart. To do that please use solution/helm/envs/*.yaml.

Don't forget to update env vars in autotests/helm/values.yaml, i.e., PARTICIPANT_NAME and api_host, to make sure that auto-tests are executed properly.

Models

For this challenge, you must use the following models. Model's performance optimization is not allowed.

Hardware

Your submission will be deployed on a g4dn.2xlarge instance (see AWS specs), so please bear in mind the hardware limitations when developing your service.

Request format

The body of the request for inference only has a text:

curl --request POST \
  --url http://localhost:8000/process \
  --header 'Content-Type: application/json' \
  --data '"This is how true happiness looks like 👍😜"'

Also you can find an example of such a request in autotests/app/src/main.js.

Response format

Your service should respond in the following format. You can also find an example of the expected response in autotests/app/src/main.js.

{
    "cardiffnlp": {
        "score": 0.2, // float
        "label": "POSITIVE" // "NEGATIVE", or "NEUTRAL"
    },
    "ivanlau": {
        "score": 0.2, // float
        "label": "English" // string, a language
    },
    "svalabs": {
        "score": 0.2, // float
        "label": "SPAM" // or "HAM"
    },
    "EIStakovskii": {
        "score": 0.2, // float
        "label": "LABEL_0" // or "LABEL_1"
    },
    "jy46604790": {
        "score": 0.2, // float
        "label": "LABEL_0" // or "LABEL_1"
    }
}

Important Notes

Performance is of paramount importance here, specifically a throughput, and it will be the determining factor in choosing the winner.
Think about error handling.
We will be stress-testing your code.
Consider the scalability and reusability of your service.
Focus on the application.

1712n/infra-challenge