Feature Request: fixed VRAM allocation pool

Abierto
#115 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
22/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
cpp

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement
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.

Lenguaje dominante
C++
Estrellas
1.2k
Forks
80
Merge medio
4 d 20 h
PR fusionados (30 d)
2

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Anbeeld/beellama.cpp

Todos los issues de Anbeeld/beellama.cpp

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.