Work out screen session count instantly with clear inputs, formula shown and shareable results.
Every detached screen or tmux window holds a shell and usually a child process open indefinitely, so abandoned sessions accumulate memory and process slots on shared bastion hosts. A hundred sessions with five windows each is 500 shells and around 1,500 processes doing nothing, which also inflates the task count against pid_max.
Session footprint
sessions = engineers x sessions each; windows = sessions x windows per session; memory = windows x per-window memory
Yes, on shared hosts. A scheduled job that kills sessions idle beyond a threshold prevents indefinite accumulation, provided users are warned.
Marginally, and it handles reattachment and pane management better. The dominant cost in both is the shells and their children, not the multiplexer itself.