Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!genrad!panda!talcott!harvard!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.ARPA (Doug Gwyn )
Newsgroups: net.unix,net.unix-wizards
Subject: Re: Help Measuring Fork/Exec Overhead
Message-ID: <907@brl-tgr.ARPA>
Date: Thu, 22-Aug-85 18:23:07 EDT
Article-I.D.: brl-tgr.907
Posted: Thu Aug 22 18:23:07 1985
Date-Received: Sun, 25-Aug-85 01:31:55 EDT
References: <782@druak.UUCP>
Organization: Ballistic Research Lab
Lines: 5
Xref: watmath net.unix:5453 net.unix-wizards:14536

UNIX System V Release 2 fork() overhead is fairly small if you
don't modify much data in the child process, because it uses
"copy on write" to avoid unnecessary copying of data from parent
into the child process.  This is a big win in most forks, which
are almost immediately followed by exec().