apunkt/omnigraph
1
0
Fork 0
mirror of https://github.com/ModernRelay/omnigraph.git synced 2026-06-09 01:35:18 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #37 from ModernRelay/test/lance-mem-pool-size

Browse source 
Raise LANCE_MEM_POOL_SIZE to 1 GB in .cargo/config.toml
This commit is contained in:
Andrew Altshuler 2026-04-20 01:22:58 +03:00 • committed by GitHub
commit a56f1d140a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

22
.cargo/config.toml Normal file
View file

@ -0,0 +1,22 @@
# Cargo config for the omnigraph workspace.
#
# `[env]` entries here apply to anything cargo launches in this repo —
# `cargo build`, `cargo test`, `cargo run`. Shipped binaries are NOT
# affected: the env var lives only in the cargo-launched process, not in
# release artifacts or Docker images.
[env]
# Lance's DataFusion memory pool per `Omnigraph` instance. Lance defaults
# to 100 MB (`lance-datafusion/src/exec.rs`), which is fine for a single
# server process in production.
#
# Under `cargo test` it's a problem: the omnigraph-server integration
# suite spins up many `Omnigraph` instances in parallel (one per test,
# default `num_cpus` threads), each with concurrent BTree index builds
# sharing that test's 100 MB pool — saturates quickly and surfaces as
# `Not enough memory to continue external sort` / `0.0 B remain
# available for the total pool`.
#
# 1 GB is comfortable headroom per-test pool; prod and CI-for-prod
# builds set the variable themselves (or keep the 100 MB default).
LANCE_MEM_POOL_SIZE = "1073741824"