Skip to content

Commit b6d4c7a

Browse files
authored
Add more spacing to the CPU based model instructions
1 parent 6a9f91a commit b6d4c7a

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

site-src/guides/index.md

+4-5
Original file line numberDiff line numberDiff line change
@@ -42,11 +42,10 @@ This quickstart guide is intended for engineers familiar with k8s and model serv
4242

4343
This setup is using the formal `vllm-cpu` image, which according to the documentation can run vLLM on x86 CPU platform.
4444
For this setup, we use approximately 9.5GB of memory and 12 CPUs for each replica.
45-
While it is possible to deploy the model server with less resources, this is not recommended.
46-
For example, in our tests, loading the model using 8GB of memory and 1 CPU was possible but took almost 3.5 minutes and inference requests took unreasonable time.
47-
In general, there is a tradeoff between the memory and CPU we allocate to our pods and the performance. The more memory and CPU we allocate the better performance we can get.
48-
After running multiple configurations of these values we decided in this sample to use 9.5GB of memory and 12 CPUs for each replica, which gives reasonable response times. You can increase those numbers and potentially may even get better response times.
49-
For modifying the allocated resources, adjust the numbers in `./config/manifests/vllm/cpu-deployment.yaml` as needed.
45+
46+
While it is possible to deploy the model server with less resources, this is not recommended. For example, in our tests, loading the model using 8GB of memory and 1 CPU was possible but took almost 3.5 minutes and inference requests took unreasonable time. In general, there is a tradeoff between the memory and CPU we allocate to our pods and the performance. The more memory and CPU we allocate the better performance we can get.
47+
48+
After running multiple configurations of these values we decided in this sample to use 9.5GB of memory and 12 CPUs for each replica, which gives reasonable response times. You can increase those numbers and potentially may even get better response times. For modifying the allocated resources, adjust the numbers in [cpu-deployment.yaml](https://github.com/kubernetes-sigs/gateway-api-inference-extension/raw/main/config/manifests/vllm/cpu-deployment.yaml) as needed.
5049

5150
Deploy a sample vLLM deployment with the proper protocol to work with the LLM Instance Gateway.
5251
```bash

0 commit comments

Comments
 (0)