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!lll-winken.llnl.gov!decwrl!purdue!news.bu.edu!usenet From: Mikhail Teterin <mi@ALDAN.star89.galstar.com> Newsgroups: comp.unix.bsd.freebsd.misc,comp.unix.advocacy Subject: Re: Win32 CreateThread() vs Unix fork() Date: Tue, 12 Dec 1995 11:16:21 -0500 Organization: Zion Elders of SCS Lines: 17 Message-ID: <30CDAAD5.1CFBAE39@ALDAN.star89.galstar.com> References: <4ab85f$idq@news.voicenet.com> <4adu72$nkf@heathers.stdio.com> <4aig98$mca@madeline.INS.CWRU.Edu> NNTP-Posting-Host: ppp-73-4.bu.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 2.0b3 (X11; I; FreeBSD 2.1.0-950928-SNA0 i386) Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:10285 comp.unix.advocacy:12088 Gabriel N. Schaffer wrote: > > Of course not, they have no choice. pcthreads library? > > That doesn't make it fast. A fork() generally takes 3ms, while creating a > thread is about .3ms on the same machine. Aha. You make 10 processes vs 10 threads and you loose 27ms (-: Making much more does not seem to make sence, since there are no machines around with this many processors. Plus. You've made a thread, now what? Now you have to start worrying about synchronization, etc. Ot not you, you just link with MT-safe libraries which worry for you, but you pay for it... After fork() processes are ready to go/use. -mi