ipex-llm/docker/llm/serving/cpu/docker
2025-02-07 11:12:42 +08:00
..
benchmark_vllm_throughput.py Docs: Fix CPU Serving Docker README (#11351) 2024-06-18 16:27:51 +08:00
Dockerfile Fix cpu serving docker image (#12783) 2025-02-07 11:12:42 +08:00
model_adapter.py.patch Refactor bigdl.llm to ipex_llm (#24) 2024-03-22 15:41:21 +08:00
payload-1024.lua LLM: Add CPU vLLM entrypoint (#11083) 2024-05-24 09:16:59 +08:00
README.md update docker image tag to 2.2.0-SNAPSHOT (#11904) 2024-08-23 13:57:41 +08:00
start-fastchat-service.sh LLM: Add CPU vLLM entrypoint (#11083) 2024-05-24 09:16:59 +08:00
start-vllm-service.sh LLM: Fix vLLM CPU version error (#11206) 2024-06-04 19:10:23 +08:00
vllm_offline_inference.py LLM: Fix vLLM CPU version error (#11206) 2024-06-04 19:10:23 +08:00

Build/Use IPEX-LLM-serving cpu image

Build Image

docker build \
  --build-arg http_proxy=.. \
  --build-arg https_proxy=.. \
  --build-arg no_proxy=.. \
  --rm --no-cache -t intelanalytics/ipex-llm-serving-cpu:2.2.0-SNAPSHOT .

Use the image for doing cpu serving

You could use the following bash script to start the container. Please be noted that the CPU config is specified for Xeon CPUs, change it accordingly if you are not using a Xeon CPU.

#/bin/bash
export DOCKER_IMAGE=intelanalytics/ipex-llm-serving-cpu:2.2.0-SNAPSHOT

sudo docker run -itd \
        --net=host \
        --cpuset-cpus="0-47" \
        --cpuset-mems="0" \
        --memory="32G" \
        --name=CONTAINER_NAME \
        --shm-size="16g" \
        $DOCKER_IMAGE

After the container is booted, you could get into the container through docker exec.

FastChat serving engine

To run FastChat-serving using IPEX-LLM as backend, you can refer to this document.

vLLM serving engine

To run vLLM engine using IPEX-LLM as backend, you can refer to this document.

We have included multiple example files in /llm/:

  1. vllm_offline_inference.py: Used for vLLM offline inference example
  2. benchmark_vllm_throughput.py: Used for benchmarking throughput
  3. payload-1024.lua: Used for testing request per second using 1k-128 request
  4. start-vllm-service.sh: Used for template for starting vLLM service
Online benchmark throurgh api_server

We can benchmark the api_server to get an estimation about TPS (transactions per second). To do so, you need to start the service first according to the instructions in this section.

In container, do the following:

  1. modify the /llm/payload-1024.lua so that the "model" attribute is correct. By default, we use a prompt that is roughly 1024 token long, you can change it if needed.
  2. Start the benchmark using wrk using the script below:
cd /llm
# You can change -t and -c to control the concurrency.
# By default, we use 12 connections to benchmark the service.
wrk -t4 -c4 -d15m -s payload-1024.lua http://localhost:8000/v1/completions --timeout 1h

Offline benchmark through benchmark_vllm_throughput.py

We have included the benchmark_throughput script provied by vllm in our image as /llm/benchmark_vllm_throughput.py. To use the benchmark_throughput script, you will need to download the test dataset through:

wget https://huggingface.co/datasets/anon8231489123/ShareGPT_Vicuna_unfiltered/resolve/main/ShareGPT_V3_unfiltered_cleaned_split.json

The full example looks like this:

cd /llm/

wget https://huggingface.co/datasets/anon8231489123/ShareGPT_Vicuna_unfiltered/resolve/main/ShareGPT_V3_unfiltered_cleaned_split.json

export MODEL="YOUR_MODEL"

# You can change load-in-low-bit from values in [sym_int4, fp8, fp16]

python3 /llm/benchmark_vllm_throughput.py \
    --backend vllm \
    --dataset /llm/ShareGPT_V3_unfiltered_cleaned_split.json \
    --model $MODEL \
    --num-prompts 1000 \
    --seed 42 \
    --trust-remote-code \
    --enforce-eager \
    --dtype bfloat16 \
    --device cpu \
    --load-in-low-bit sym_int4