Files
project_6/computility-run.yaml
Claude 57a2216143 fix: max_num_seqs=2 for n=2 support + remove protocol n clamp
Sub168 (competitor) passes t2_n_2 with n=2 at 1.50s even with
max_num_seqs likely >1. Our max_num_seqs=1 made n=2 crash.

Changes:
- computility-run.yaml: max-num-seqs 1→2 (200GB total VRAM sufficient)
- protocol.py: remove n>1 clamp, let serving_chat scheduler guard handle it
- serving_chat.py retains try/except guard for get_scheduler_config

Risk: if 2 concurrent seqs OOM, service crashes. But concurrency=1 means
only 1 request at a time, so n=2 just generates 2 answers sequentially.

CCCL input: tuning_topk.cuh (bits_per_pass=11 for float32, threads=512),
tuning_transform.cuh (cc_to_min_bytes_in_flight: B200=64KB, A100=16KB,
BI-V100 should use 48-64KB based on per-SM BW=56GB/s)
2026-08-07 08:18:41 +00:00

51 lines
1.3 KiB
YAML

concurrency: 1
command:
- python3
- -m
- vllm.entrypoints.openai.api_server
- --model
- /model
- --served-model-name
- llm
- --max-model-len
- '100000'
- --gpu-memory-utilization
- '0.90'
- --trust-remote-code
- -tp
- '4'
- --max-num-seqs
- '2'
- --disable-log-requests
- --disable-frontend-multiprocessing
- --enforce-eager
- --enable-auto-tool-choice
- --tool-call-parser
- qwen3_coder
- --reasoning-parser
- qwen3
- --enable-prefix-caching
- --dtype
- half
env:
- name: VLLM_ENGINE_ITERATION_TIMEOUT_S
value: '3600'
- name: VLLM_ATTENTION_BACKEND
value: XFORMERS
- name: ENABLE_CUSTOM_IPC
value: '1'
- name: PYTHONPATH
value: /usr/local/corex/lib/python3/dist-packages:/usr/local/corex/lib64/python3/dist-packages
- name: LD_LIBRARY_PATH
value: /usr/local/corex/lib64:/usr/local/openmpi/lib
- name: VLLM_COREX_FA2_LIBRARY
value: /usr/local/corex/lib64/libcorex_fa2.so
- name: VLLM_COREX_GDN_LIBRARY
value: /usr/local/corex/lib64/libcorex_gdn.so
- name: VLLM_COREX_MOE_LIBRARY
value: /usr/local/corex/lib64/libcorex_moe.so
- name: VLLM_REQUEST_METRICS_FILE
value: /tmp/vllm-request-metrics.jsonl
- name: VLLM_CACHE_BLOCK_SIZE
value: '16'