Eric Wong [off-list ref] writes:
How big is the parent process which forks the git commands? On Linux at
least, fork() performance is negatively impacted by parent process
memory size.
Huh. I thought with the advent of demand-paging, at the very least with
copy-on-write, this was supposed to be sort of a non-issue.
The old original UNIX version, in contrast, consisted of swapping out
the current process without removing the in-memory copy. But since the
in-memory copy then did the exec call and since usually the exec call
was happy about every page of free memory (we _are_ talking about
something like 64kB of total available memory here), that tended to work
reasonably well.
--
David Kastrup