V8 Heap Generations and GC Tuning

Understand how V8's generational garbage collector and --max-old-space-size affect Node.js memory limits.

In a Node.js process, you set --max-semi-space-size=64 but memory-heavy short-lived allocations still trigger frequent full GCs and rising latency. Which statement best explains V8's generational GC behavior and this flag's role?