Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.hawaii.edu!ames!hookup!jussieu.fr!univ-lyon1.fr!in2p3.fr!swidir.switch.ch!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!in2.uu.net!news.voicenet.com!news From: 900RR (900RR) Newsgroups: comp.unix.bsd.freebsd.misc,comp.unix.advocacy Subject: Win32 CreateThread() vs Unix fork() Date: Sat, 09 Dec 1995 05:45:50 GMT Organization: Voicenet - Internet Access - (215)674-9290 Lines: 28 Message-ID: <4ab85f$idq@news.voicenet.com> NNTP-Posting-Host: philly28.voicenet.com X-Newsreader: Forte Free Agent v0.55 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:10767 comp.unix.advocacy:12362 Win32's CreateThread() is an extremely fast and efficient way of implementing multi-threaded, multi-user server applications (like Web servers). Threads are then run on individual processors in SMP boards, further boosting throughput. By contrast, Unix uses fork() to start an entire new process to service client requests. MP unixes could then run these whole processes on different CPU's. In any case, does anyone know how much more efficient a server application could run under an NT system than the same app, same hardware on something like FreeBSD or Linux? Do veteran Unix programmers avoid fork() like the plague? Thanks CBR