github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 08:02:14 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #11092] Loading time of mistral-small3.1 is too long #11087 #53829

New Issue
Closed
opened 2026-04-29 04:50:16 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-29 04:50:16 -05:00
Owner
Copy Link

Originally created by @JitaekJo on GitHub (Jun 17, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11092

What is the issue?

Image

A related problem is the model isn't loaded. As you can see, even though the memory is loaded and ollama is served after providing a prompt, the load is "0%" for a long time.
Is it related to the memory issue? I'm doubt.

######################################################################
I've upgraded ollama recently yes.

Mystery solved.

There have been recent changes to the estimation logic to reduce the chance of an OOM. You can force ollama to load more layers into GPU by setting num_gpu as described https://github.com/ollama/ollama/issues/6950#issuecomment-2373663650. This may increase OOMs or cause a https://github.com/ollama/ollama/issues/7584#issuecomment-2466715900.

And this doesn't seem like an resolution because this guides to load the model on RAM and CPU.
My problem is that the model isn't loaded.

Relevant log output

OS

Windows

GPU

Nvidia

CPU

Intel

Ollama version

0.9.0

Originally created by @JitaekJo on GitHub (Jun 17, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11092 ### What is the issue? ![Image](https://github.com/user-attachments/assets/6944ebaa-fc4b-45d3-a65c-57e981082021) **A related problem is the model isn't loaded. As you can see, even though the memory is loaded and ollama is served after providing a prompt, the load is "0%" for a long time. Is it related to the memory issue? I'm doubt.** ###################################################################### I've upgraded ollama recently yes. Mystery solved. There have been recent changes to the estimation logic to reduce the chance of an OOM. You can force ollama to load more layers into GPU by setting num_gpu as described https://github.com/ollama/ollama/issues/6950#issuecomment-2373663650. This may increase OOMs or cause a https://github.com/ollama/ollama/issues/7584#issuecomment-2466715900. **And this doesn't seem like an resolution because this guides to load the model on RAM and CPU. My problem is that the model isn't loaded.** ### Relevant log output ```shell ``` ### OS Windows ### GPU Nvidia ### CPU Intel ### Ollama version 0.9.0
GiteaMirror added the bug label 2026-04-29 04:50:16 -05:00
GiteaMirror commented 2026-04-29 04:50:18 -05:00
Author
Owner
Copy Link

@JitaekJo commented on GitHub (Jun 17, 2025):

I found a cause of problem. When I feed an IMAGE, MISTRAL isn't be loaded. Please fix this bug.

<!-- gh-comment-id:2979323137 --> @JitaekJo commented on GitHub (Jun 17, 2025): I found a cause of problem. When I feed an IMAGE, MISTRAL isn't be loaded. Please fix this bug.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#53829
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?