Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Tests] Add allocator stress tests for large graphs

Open
  • Is something wrong?
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
62/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
cpp
Domain
testing-qa

Research direction

Start in tests/test-alloc.cpp and read the allocator interface in ggml/include/ggml-alloc.h, then review the existing 12 tests and their buffer sizes. Add the five requested stress-test cases for deep, wide, diamond, view-heavy, and memory-pressure graphs using MB-scale tensors. Done means all listed tests verify allocation and non-overlap, including the requested performance time bounds.

Written by the indexing model from the issue text.

Description

stale

Summary

Extend tests/test-alloc.cpp with stress tests for large/complex computation graphs.

Current State

  • test-alloc.cpp has 12 tests covering basic scenarios
  • Tests use small buffer sizes (16-64 bytes)
  • Limited coverage for complex graph topologies

Missing Stress Tests

  1. Deep graph chains: 100+ node sequential dependencies
  2. Wide graphs: Many parallel branches merging at end
  3. Diamond patterns: Common in residual connections (A -> B -> D, A -> C -> D)
  4. View-heavy graphs: Heavy use of reshape/permute/view operations
  5. Memory pressure: Near-full cache eviction scenarios

Test Requirements

  • Use realistic tensor sizes (MB range)
  • Verify no memory overlap violations
  • Verify all tensors are allocated
  • Check allocator performance (time bounds)

Acceptance Criteria

  • Add test_deep_chain() - 100+ sequential ops
  • Add test_wide_merge() - many parallel branches
  • Add test_diamond_pattern() - residual-like topology
  • Add test_view_chains() - complex view operations
  • Add test_memory_pressure() - near-full scenarios

Related Files

  • tests/test-alloc.cpp
  • ggml/include/ggml-alloc.h
Dominant language
C++
Stars
1
Forks
0
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jose-compu/funes.cpp

All issues in jose-compu/funes.cpp

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.