Skip to content

Commit 4c54fe3

Browse files
CopilotSkafteNicki
andcommitted
Remove Cortex from ML deployment frameworks list
Co-authored-by: SkafteNicki <24896311+SkafteNicki@users.noreply.github.com>
1 parent 8ff9cb0 commit 4c54fe3

1 file changed

Lines changed: 2 additions & 3 deletions

File tree

s7_deployment/ml_deployment.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,6 @@ table = "| 🌟 Framework | 🧩 Backend Agnostic | 🧠 Model Agnostic | 📂
4242
table += "|--------------|---------------------|-------------------|---------------|----------------|\n"
4343

4444
data = [
45-
("Cortex", "Yes", "Yes", "cortexlabs/cortex"),
4645
("BentoML", "Yes", "Yes", "bentoml/bentoml"),
4746
("Ray Serve", "Yes", "Yes", "ray-project/ray"),
4847
("Triton Inference Server", "Yes", "Yes", "NVIDIA/triton-inference-server"),
@@ -64,9 +63,9 @@ for framework, backend_agnostic, model_agnostic, repo in data:
6463
print(table)
6564
```
6665

67-
The first 7 frameworks are backend agnostic, meaning that they are intended to work with whatever computational backend
66+
The first 6 frameworks are backend agnostic, meaning that they are intended to work with whatever computational backend
6867
your model is implemented in (TensorFlow, PyTorch, Jax, Sklearn, etc.), whereas the last 3 are backend specific (PyTorch,
69-
TensorFlow and a custom framework). The first 9 frameworks are model agnostic, meaning that they are intended to work
68+
TensorFlow and a custom framework). The first 8 frameworks are model agnostic, meaning that they are intended to work
7069
with whatever model you have implemented, whereas the last one is model specific in this case to LLM's. When choosing a
7170
framework to deploy your model, you should consider the following:
7271

0 commit comments

Comments
 (0)