| Title: | DEC Rdb against the World |
| Moderator: | HERON::GODFRIND |
| Created: | Fri Jun 12 1987 |
| Last Modified: | Thu Feb 23 1995 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1348 |
| Total number of notes: | 5438 |
I've been reading some of the Oracle V6/TPO manuals and came across
something called the "two task" architecture. Oracle describes
it as follows.
In the two task architecture ON THE SAME SYSTEM, your programs are
linked to a set of sharable routines and runtime libraries. The Oracle
database software which does the read and writes are linked to a copy
of the same routines. The database software and your applications talk
to each other via SQL*net via VMS mailboxes.
Oracle is saying that this help you maintain portability since you
don't have to relink Oracle if you install a new release of VMS
and/or you don't have to relink your programs if you install a new
release of Oracle. They also add that there is about a 5% performance
hit when using the two task architecture.
I wonder if this is Oracle's attempt to counter Ingres multi-threaded
server. I also wonder what, if any, the implication for using VMS
mailboxes.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 437.1 | uh-huh... | DPDMAI::DAVISGB | Gil Davis DTN 554-7245 | Mon Sep 25 1989 21:39 | 8 |
Interesting about the relinking also....
I remember hearing about a benchmark on the west coast where Oracle had
to be reinstalled to change the memory size on a 6000 class machine...I
wonder if applications need to be re-linked also...? (kind of an
aside...)
| |||||