Thread View: net.database
2 messages
2 total messages
Started by Palat
Thu, 22 Aug 1985 22:31
Ingres log in time
Author: Palat
Date: Thu, 22 Aug 1985 22:31
Date: Thu, 22 Aug 1985 22:31
11 lines
962 bytes
962 bytes
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. Mohan Palat
Re: Ingres log in time
Author: Jeff Anton
Date: Sat, 24 Aug 1985 17:46
Date: Sat, 24 Aug 1985 17:46
21 lines
1453 bytes
1453 bytes
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
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads