high severityvespa-engine tensor attributes
Huge memory consumption by sparse tensor fields (e.g., doubling memory usage when adding similar fields); potential OOM or spikes during feeding/indexing large datasets.
Root cause
Sparse tensor attribute fields are stored entirely in memory by default without pagination support, leading to high memory usage for large datasets. `attribute: paged` was not supported for non-dense tensors until later versions, forcing full in-memory storage and potential spikes when scaling documents or adding fields.
vespatensorsparse tensormemory spikepaged attributeattribute