Reviewed by Aditya Kumar Β· Last reviewed 2026-03-24
Virtual memory: Each process gets large address space; OS maps pages to physical frames; demand paging; swap when RAM full. WHY: Isolation; working set > RAM. For DE: Excessive swap (si/so in vmstat) kills performance. SCALABILITY: Size Spark executors to avoid swap....
Virtual memory: Each process gets large address space; OS maps pages to physical frames; demand paging; swap when RAM full. WHY: Isolation; working set > RAM. For DE: Excessive swap (si/so in vmstat) kills performance. SCALABILITY: Size Spark executors to avoid swap. COST: Swap is 1000x slower than RAM; tune JVM heap to leave OS headroom.
Red Flag: Ignoring swap. Pro-Move: 'We monitor si/so; Spark executors sized at 80% of node memory; no swap in 2 years on prod.'
According to DataEngPrep.tech, this is one of the most frequently asked General/Other interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.