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

[GH-ISSUE #6200] Support --mlock on the command line. Also there are undocumented model file parameters #65910

New Issue
Open
opened 2026-05-03 23:08:05 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-03 23:08:05 -05:00
Owner
Copy Link

Originally created by @sdmorrey on GitHub (Aug 6, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/6200

What is the issue?

The original issue was that my Mac was experiencing an exponential slow down. Upon investigating the issue I noticed my RAM usage was very, very low, but my swap was climbing at the rate of about 1GB per 1K of filled context.

In the end I discovered the --mlock flag in llama.cpp.
I was in discord asking for help setting it since the command line Ollama straight up rejects it.

Eventually we discovered that this is controlled by the model file parameter use_mlock

Except that appears to be undocumented. In the same space I found a few other undocumented parameters.

So in a nutshell, it would lovely if you could add --mlock to the command line since I don't want to have to edit every model file. Also if you could update the docs so use_mlock and the other undocumented parameters are documented, that would be awesome.

Thanks for your hard work and such a great product!

OS

macOS

GPU

Intel

CPU

Intel

Ollama version

0.3.3

Originally created by @sdmorrey on GitHub (Aug 6, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/6200 ### What is the issue? The original issue was that my Mac was experiencing an exponential slow down. Upon investigating the issue I noticed my RAM usage was very, very low, but my swap was climbing at the rate of about 1GB per 1K of filled context. In the end I discovered the --mlock flag in llama.cpp. I was in discord asking for help setting it since the command line Ollama straight up rejects it. Eventually we discovered that this is controlled by the model file parameter use_mlock Except that appears to be undocumented. In the same space I found a few other undocumented parameters. So in a nutshell, it would lovely if you could add --mlock to the command line since I don't want to have to edit every model file. Also if you could update the docs so use_mlock and the other undocumented parameters are documented, that would be awesome. Thanks for your hard work and such a great product! ### OS macOS ### GPU Intel ### CPU Intel ### Ollama version 0.3.3
GiteaMirror added the bug label 2026-05-03 23:08:05 -05:00
GiteaMirror commented 2026-05-03 23:08:07 -05:00
Author
Owner
Copy Link

@sdmorrey commented on GitHub (Aug 6, 2024):

Forgot to mention, I'll be glad to submit a PR if that would be welcome. I just want to make sure it's an oversight and not a design decision for reasons I'm just not aware of.

Thanks!

<!-- gh-comment-id:2271304884 --> @sdmorrey commented on GitHub (Aug 6, 2024): Forgot to mention, I'll be glad to submit a PR if that would be welcome. I just want to make sure it's an oversight and not a design decision for reasons I'm just not aware of. Thanks!
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#65910
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?