Background Process Calculator
Calculate combined resource footprint of background processes running via nohup or &.
About Background Process Calculator
Processes started with `nohup command &` or detached from the shell via `disown` keep running after the launching terminal session ends, since nohup blocks SIGHUP from reaching them and disown removes them from the shell's job table — but they remain ordinary processes consuming real memory and CPU, just without a visible controlling terminal or easy `jobs`-based tracking. Summing their estimated footprint (count × average RSS, count × average CPU%) gives a rough resource allocation figure, which is also a useful prompt to consider whether ad-hoc background processes should instead be proper supervised services (systemd units, or a task queue) with defined resource limits and restart behavior.
Formula
Total background resource footprint
total_rss = count × avg_rss; total_cpu_cores = (count × avg_cpu%) / 100
- n
- background process count
- "\\bar{r}"
- average RSS per process
- "\\bar{c}"
- average CPU% per process
Worked example
With the default values below, Background Process Calculator returns Total Estimated Memory (MB) of 900.0. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Number of Background (nohup/disown) Processesminimum 0
- 6
- Average RSS per Process (MB)minimum 0
- 150
- Average CPU % per Process (of one core)accepts 0–100
- 15
- CPU Cores Availableminimum 1
- 8
Results
- Total Estimated Memory (MB)
- 900.0
- Total CPU (core-equivalent)
- 0.900
- As % of Total Core Capacity
- 11.25%
- Note
- Background processes have a light overall CPU footprint relative to available capacity.
Step by step
- 1Values used
- 2Total background resource footprint
- 3Total Estimated Memory (MB)= 900.0
- 4Total CPU (core-equivalent)= 0.900
- 5As % of Total Core Capacity= 11.25
- 6Note= Background processes have a light overall CPU footprint relative to available capacity.
Assumptions and limits
- The result is derived only from the 4 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
- Figures are rounded for display to 3 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
What's the difference between nohup and disown?
nohup launches a process with SIGHUP ignored from the start, so it survives the terminal closing even if you never manually detach it. disown instead removes an already-running background job from the current shell's job table (so the shell no longer sends it SIGHUP on exit), typically used on a job you started with `&` and later decide should survive the session ending.
How do I find all nohup/disowned background processes running on a system?
There's no dedicated tracking mechanism — since these are just ordinary processes without a controlling terminal, `ps -eo pid,tty,cmd | grep '?'` (TTY shown as '?') is a reasonable heuristic to surface terminal-less processes, though it also catches legitimately daemonized services, not exclusively ad-hoc background jobs.
Why is relying on nohup/disown for long-running work considered poor practice?
These processes have no supervision — if they crash, nothing restarts them; if the system reboots, they're gone with no automatic recovery; and there's no built-in resource limiting or centralized logging. A systemd service (or a proper job queue/task runner) provides restart policies, resource limits (via cgroups), and log integration that ad-hoc background processes lack entirely.