BGE Large EN v1.5 needs ~2.9 GB VRAM. Intel Arc A370M 4GB has 4.0 GB. With F16 quantization, expect ~5 tok/s.
Operating mode
Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.
Current mode
Balanced
Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.
Select quantization to explore
Fit status
Runs well
Decode
4.7 tok/s
TTFT
41279 ms
Safe context
512
Memory
2.9 GB / 4.0 GB
This model fits, but memory bandwidth is the part holding decode speed back.
Throughput will feel slow
Estimated decode speed is only 4.7 tok/s, so this is more of a technical fit than a comfortable daily-driver setup.
Runtime ecosystem is narrower than CUDA
Intel GPUs can look attractive on memory per dollar, but local AI tooling, kernels, and model coverage are still broader and easier on CUDA today.
Prioritize bandwidth, not only capacity
If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.
Prefer CUDA if you want the path of least resistance
If your goal is maximum runtime coverage, easier troubleshooting, and better support for new local AI releases, CUDA is usually still the safer upgrade path.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | A | Runs well | 4.7 tok/s | 22516 ms | 512 |
| Coding | A | Runs well | 4.7 tok/s | 41279 ms | 512 |
| Agentic Coding | B | Runs with offload (needs ~0.1 GB host RAM) | 4.7 tok/s | 60043 ms | 512 |
| Reasoning | A | Runs well | 4.7 tok/s | 48785 ms | 512 |
| RAG | B | Runs with offload (needs ~0.1 GB host RAM) | 4.7 tok/s | 75053 ms |
How BGE Large EN v1.5 (0.33500000834465027B params) fits at each quantization level on Intel Arc A370M 4GB (4.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 0.1 GB | Low | S85 |
Q3_K_S | 3 | 0.2 GB | Low | S86 |
NVFP4 | 4 |
Copy-paste commands to run BGE Large EN v1.5 on your machine.
Run
docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
--hf-repo "BAAI/bge-large-en-v1.5" \
--hf-file "bge-large-en-v1.5-F16.gguf" \
-c 4096 -ngl 99Your hardware
| Model | Params | Grade | Decode | Capabilities |
|---|---|---|---|---|
 Phi-4 Mini Reasoning 4B | 3.8B | A | 15 tok/s | |
 Jina Embeddings v3 | 0.57B | A | 8 tok/s | |
Yes, Intel Arc A370M 4GB can run BGE Large EN v1.5 with a A grade (Runs well). Expected decode speed: 4.7 tok/s.
BGE Large EN v1.5 (0.33500000834465027B parameters) requires approximately 2.9 GB of memory with F16 quantization.
The recommended quantization for BGE Large EN v1.5 is F16, which balances quality and memory efficiency.
On Intel Arc A370M 4GB, BGE Large EN v1.5 achieves approximately 4.7 tokens per second decode speed with a time-to-first-token of 41279ms using F16 quantization.
For coding workloads, BGE Large EN v1.5 on Intel Arc A370M 4GB receives a A grade with 4.7 tok/s and 512 context.
On Intel Arc A370M 4GB, BGE Large EN v1.5 can safely use up to 512 tokens of context. The model's official context limit is 512, but available memory constrains the safe maximum.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/bge-large-en-v1.5-on-arc-a370m-4gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview:
| 512 |
0.2 GB |
| Medium |
| S86 |
Q4_K_M | 4 | 0.2 GB | Medium | S86 |
Q5_K_M | 5 | 0.2 GB | High | S86 |
Q6_K | 6 | 0.3 GB | High | S86 |
Q8_0 | 8 | 0.4 GB | Very High | S87 |
F16Best for your GPU | 16 | 0.7 GB | Maximum | S87 |
 BGE M3 |
| 0.57B |
| S |
| 8 tok/s |
Prioritize bandwidth, not only capacity. If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.
Often yes, if your goal is the easiest setup and the widest runtime support. Intel can offer attractive memory capacity, but CUDA still tends to win on tooling maturity, guides, kernels, and model coverage for local AI.