OOM on 32GB while running auto-opt Qwen/Qwen2.5-Coder-7B-Instruct
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.4k
- Forks
- 315
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 16
Description
Hi,
I've been playing around with olive after being frustrated with the limited amounts of models available for my "AI" PC. Anyhow, I have been trying to run the following on a 32GB Lenovo Yoga Slim 7x as well as a dedicated cloud server with 32GB:
olive auto-opt \
--model_name_or_path "$CACHE_MODEL_PATH" \
$TRUST_FLAG \
--output_path "$OUTPUT_PATH" \
--device "$DEVICE" \
--provider "$PROVIDER" \
--use_ort_genai \
--precision "$PRECISION" \
--log_level "$LOG_LEVEL" \
$EXTRA_ARGS
with the following parameters
==========================================
QNN Model Conversion Container
==========================================
Model: Qwen/Qwen2.5-Coder-7B-Instruct
Output Directory: .
Output Name: qwen-coder-7b
Precision: int4
Device: npu
Provider: QNNExecutionProvider
Cache Directory: model-cache
==========================================
But no matter what I run into an OOM error:
[ 1299.228531] Out of memory: Killed process 11552 (olive) total-vm:43667312kB, anon-rss:31484340kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:64956kB oom_score_adj:0
Is this expected? If so is there any way to reduce the memory load while keeping the model "intelligent"? Originally I had planned on converting the devstral-23b from Mistral to finally run on my Qualcomm NPU, but as it seems that will continue to be a dream.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the olive auto-opt command with the reported Qwen/Qwen2.5-Coder-7B-Instruct, int4, NPU, and QNNExecutionProvider settings on a 32GB system. Trace the command's memory use and determine whether the OOM is expected; done means documenting the cause and any supported way to reduce memory while preserving the requested conversion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100