ADVICE: VMS TWO-TASK mode.

From: <pihlab_at_hhcs.gov.au>
Date: 11 Feb 93 11:05:21 +1100
Message-ID: <1993Feb11.110522.618_at_hhcs.gov.au>


We are currently running   

  • Oracle V6.0.36.5 in SINGLE-TASK mode,
  • on a VAX 9420 (each CPU 80% utilized),
  • running VMS 5.5-2,
  • with 1Gig of RAM (70% utilized),
  • 130 concurrent users (3000 registered),
  • Production DB has SGA size of 8192, and
  • All user accounts have WSDEF=WSQUOTA=WSEXTENT=8192 (as recommended by an ORACLE Oracle/VMS guru).

We are now looking at moving to TWO-TASK operation prior to the arrival of a production copy of Oracle V7 and I would like to here from anyone who is using TWO-TASK and what traps I should be aware of.

I've been informed that TWO-TASK will

  • require a relink of the kernel and all products,
  • add an extra overhead of 3-5% resource usage,
  • double the number of processes on the machine,
  • Oracle V7 will reduce these overheads significantly.

I need to know

  • how will it affect memory usage?
  • how will it affect paging?
  • what account is the "shadow" process run under (ORACLE or the user's)?
  • what are the advantages of going to TWO-TASK?
  • Is this a good thing to do or are we wasting our time?
  • Should we wait for Oracle V7 to arrive?

Send replies to my EMail address and I will summarize for the news group.

Thankyou.

-- 

Bruce...        pihlab_at_hhcs.gov.au

"If you swallow a live frog first thing in the morning ...
 Nothing worse will happen to either of you for the rest of the day."

*******************************************************************
* Bruce Pihlamae  --  Database Administration                     *
* Commonwealth Department of Health, Housing & Community Services *
* Canberra, Australia                             (W) 06-289-7056 *
*******************************************************************
* These are my own thoughts and opinions, few that I have.        *
*******************************************************************
Received on Thu Feb 11 1993 - 01:05:21 CET

Original text of this message