Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!tut.cis.ohio-state.edu!uccba!spca6!ray
From: ray@spca6.UUCP (ray)
Newsgroups: comp.databases
Subject: Re: unify 3.2 and 4.0 selsort() problems
Keywords: unisort()==fork()
Message-ID: <300@spca6.UUCP>
Date: 18 Jan 89 04:55:21 GMT
References: <1074@wpg.UUCP> <24897@sgi.SGI.COM> <1081@wpg.UUCP> <1995@lznh.UUCP>
Reply-To: ray@spca6.UUCP (ray)
Organization: 6th Circuit Court of Appeals;Cincinnati
Lines: 16

In article <1995@lznh.UUCP> ariel@lznh.UUCP (<10000>Ariel Aloni) writes:
>In my experience, the most stable library call is unisort(). You can
>do practically anything with it although it's sometimes a bit more
>expensive.
Just something every Unify HLI user should know, any call to unisort is
will cause a fork() system call.  This is implicit in the manual, but
should really be brought to every one's attention.  On most systems, the
fork() will be a little more than just 'a bit more expensive' than a
selsort().
In fact, one of our programmers had written a program that was spending 
33% of it's time executing fork() for the unisort() calls he had coded.
(I seriouly considered removing it from our copy of the library when his reply
was "But, unisort is SOOOOOOOO easy to use!" AARRRRRGGGGGHHHH!)
Learn to use selsort, it works!(at least in our copy of 3.2 and 4.0)
=
ray mit-eddie!uccba!spca6!ray