Feature Request: fixed VRAM allocation pool
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 22/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Tranquilla
- Stack tecnologico
- cpp
- Ambito
- machine-learning, performance
Direzione di ricerca
The request centres on the CUDA backend's buffer allocation, so start with ggml_backend_cuda_buffer_type_alloc_buffer in ggml/src/ggml-cuda.cu and trace where cudaMalloc is called for model weights and the KV cache. The issue proposes a fixed pool sized as a fraction of VRAM, but the design (how to size it, how to handle fragmentation and freeing) is unsettled and the code in the issue is an unverified sketch. Done would need a maintainer-agreed design before any implementation.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Prerequisites
- I am running the latest code. Mention the version if possible as well.
- I carefully followed the README.md.
- I searched using keywords relevant to my issue to make sure that I am creating a new issue that is not already open (or closed).
- I reviewed the Discussions, and have a new and useful enhancement to share.
Feature Description
It would be nice to be able to set the value of preallocated VRAM in percents like for vLLM (ex. 0.9 = 90%) and to use preallocated pool in this mode, so that extra software never influence beellama work.
Motivation
The problem: whatever manually crafted settings for beellama and model are made, the VRAM consumption is not fully controlled, because VRAM is allocated during context growth and beellama work and because other GUI applications (browsers, electron-based projects) also continue to consume extra VRAM. Currently Firefox can easily consume up to 1.5 GB vram and begin with 100 MB initially, so generation speed just drops to almost zero from unpredictable moment.
Possible Implementation
LLM based suggestions:
Method 2: Code Modification (Hard Physical Reservation Pool)
If you want llama.cpp to allocate a single massive contiguous block of VRAM (e.g., 20 GB out of 24 GB) via cudaMalloc at program start, and have GGML consume slices of that block instead of calling cudaMalloc dynamically:
Step 1: Create a Fixed Global Pool
In ggml/src/ggml-cuda.cu (or ggml-cuda.cpp), declare a static memory pool pointer and allocate it during CUDA backend initialization:
// Static preallocated pool
static void* g_cuda_vram_pool = nullptr;
static size_t g_vram_pool_offset = 0;
static size_t g_vram_pool_size = 0;
void init_cuda_vram_pool(size_t reserve_bytes) {
if (g_cuda_vram_pool != nullptr) return;
// Physically allocate the entire pool at start
cudaError_t err = cudaMalloc(&g_cuda_vram_pool, reserve_bytes);
if (err == cudaSuccess) {
g_vram_pool_size = reserve_bytes;
printf("CUDA: Preallocated %zx bytes of VRAM pool successfully.\n", reserve_bytes);
} else {
printf("CUDA: Failed to preallocate VRAM pool: %s\n", cudaGetErrorString(err));
}
}
Step 2: Override GGML's CUDA Buffer Allocation Function
In ggml-cuda.cu, locate the buffer allocation function used by the CUDA backend: ggml_backend_cuda_buffer_type_alloc_buffer.
Replace the underlying cudaMalloc call inside that function so it returns an offset pointer into g_cuda_vram_pool:
// Simplistic bump-allocator replacement inside CUDA backend
static void* pool_alloc(size_t size) {
// Maintain 256-byte alignment required by CUDA
size_t aligned_size = (size + 255) & ~255;
if (g_vram_pool_offset + aligned_size > g_vram_pool_size) {
printf("CUDA Pool Error: Out of preallocated VRAM!\n");
return nullptr;
}
void* ptr = (uint8_t*)g_cuda_vram_pool + g_vram_pool_offset;
g_vram_pool_offset += aligned_size;
return ptr;
}
// In your buffer allocation routine:
// Replace cudaMalloc(&ptr, size) with:
ptr = pool_alloc(size);
Step 3: Call Initialization in llama_backend_init
Call init_cuda_vram_pool(target_size_bytes) inside your initialization function (e.g., llama_backend_init) before loading model layers or allocating context buffers.
Result
When llama.cpp starts up, it immediately issues a single cudaMalloc call for your requested size. All model weights, KV cache matrices, and scratch workspaces allocated during token generation will be carved directly out of this existing buffer. No further calls to cudaMalloc or cudaFree will touch the driver or OS.
- Lingua principale
- C++
- Stelle
- 1.2k
- Fork
- 80
- Merge medio
- 4g 20h
- PR unite (30g)
- 2
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Anbeeld/beellama.cpp
-
[BUG] KVarN assertion failure in build_inp_mem_hybrid_iswa() due to uninitialized self_kvarn_rotAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Anbeeld/beellama.cpp#205 ·
-
Difficoltà 3/5 Mezza giornata Idoneità per principianti 58/100
Anbeeld/beellama.cpp#206 ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 57/100
Anbeeld/beellama.cpp#204 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
Anbeeld/beellama.cpp#203 · 2 commenti ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
Anbeeld/beellama.cpp#202 · 1 commento ·
Tutte le issue di Anbeeld/beellama.cpp
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
CachyOS/packageinstaller#144 ·
I maintainer di solito rispondono entro 1 giorno
-
documentation
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
TomerAberbach/profiler-md#951 ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug] Default key routing (JavaStringHash) picks a different partition than the Java client for about half of keysForse già presa @0z5a l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
apache/pulsar-client-go#1575 ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
pocoproject/poco#5764 ·
I maintainer di solito rispondono entro 2 giorni
-
bug cpp-core-guidelines low-priority
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
NatronGitHub/openfx-supportext#164 ·
I maintainer di solito rispondono entro 1 giorno