Unverified50% confidenceFactExact time
On a machine with 2 GB of memory, what actually causes OOM is often not average memory usage, but the sudden spike in peak RSS during a particular rendering or decoding step.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedOn a server with 1 vCPU / 2 GB of memory, knowing whether peak memory is approaching the OOM line is more useful than knowing average usage; ru_maxrss records the historical high-water mark and can catch short memory bursts.71% similarUnverifiedWhen memory is pushed to the limit, Linux's OOM mechanism may kill the service process due to excessive RAM usage; this can be avoided by setting oom_score_adj to -1000 to prevent the system from mistakenly killing it.71% similarUnverifiedUsing Unified Memory and letting the operating system automatically move data can drag down inference efficiency due to frequent paging under long contexts.70% similarUnverifiedWhen model size reaches about twice the physical memory, mmap-based inference schemes collapse due to a 'page-fault storm', with the operating system blindly scheduling pages and inference stuck on disk I/O.70% similarUnverifiedWhen memory scales to hundreds of MB or even GB, a pure file-based approach may still need to be combined with indexing mechanisms and vector retrieval technologies to balance simplicity and performance70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1042785API
curl https://kongchang.com/api/v1/knowledge/claims/1042785MCP
get_claim(id=1042785)