Skip to content

Commit

Permalink
[Misc][Minor] Fix CPU block num log in CPUExecutor. (vllm-project#4088)
Browse files Browse the repository at this point in the history
  • Loading branch information
bigPYJ1151 authored Apr 15, 2024
1 parent e11e200 commit 0003e91
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion vllm/executor/cpu_executor.py
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,10 @@ def initialize_cache(self, num_gpu_blocks: int,
# NOTE: We log here to avoid multiple logs when number of workers is
# greater than one. We could log in the engine, but not all executors
# have GPUs.
logger.info(f"# CPU blocks: {num_cpu_blocks}")
# NOTE: `cpu block` for CPU backend is located on CPU memory but is
# referred as `gpu block`. Because we want to reuse the existing block
# management procedure.
logger.info(f"# CPU blocks: {num_gpu_blocks}")
self.driver_worker.initialize_cache(num_gpu_blocks, num_cpu_blocks)

def execute_model(self,
Expand Down

0 comments on commit 0003e91

Please sign in to comment.