Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!ucbvax!anton
From: anton@ucbvax.ARPA (Jeff Anton)
Newsgroups: net.database
Subject: Re: Ingres log in time
Message-ID: <10182@ucbvax.ARPA>
Date: Sat, 24-Aug-85 13:46:26 EDT
Article-I.D.: ucbvax.10182
Posted: Sat Aug 24 13:46:26 1985
Date-Received: Sun, 25-Aug-85 12:58:42 EDT
References: <2671@ihuxf.UUCP>
Reply-To: anton@ucbvax.UUCP (Jeff Anton)
Distribution: net
Organization: University of California at Berkeley
Lines: 21

In article <2671@ihuxf.UUCP> mohan@ihuxf.UUCP (Palat) writes:
>	Has anyone noticed that the time to invoke ingres
>	is much more the first time after a compilation (of an equel 
>	program) than the subsequent ones? That is, if the
>	same compiled equel program is executed two or more
>	times, the time taken to log in to ingres is longer the
>	first time than the subsequent executions. Any possible
>	reasons for this? By the way, the version of ingres used
>	was AT&T INGRES.

RTI INGRES has a method of storeing query plans in equel programs.
I'm not sure but perhaps the database is conditioned or these
plans are stored durring execution.

I've not heard of AT&T INGRES.  Is it not an RTI port?
-- 
C knows no bounds.
					Jeff Anton
					U.C.Berkeley
					ucbvax!anton
					anton@BERKELEY.EDU