[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ulysse::rdb_vms_competition

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

90.0. "Oracle sizing question" by MISFIT::FLOESER (Let's talk AI/Performance/BaseStar/Baseway) Fri Mar 11 1988 21:00

In the spirit of notes 16, 24, 49, and 71, let me ask for sizing assistance
for Oracle. With a vain attempt to gather all the information that the
referenced notes request, here goes: 

Will: 
	8 (eight) Oracle users doing general updates at the rate of
	1 (one) transaction per 5 (five) seconds.  A transaction is
	an update/correction, addition or inquiry.

With a database of:

	7,000,000 (seven million) records, (currently at 3.5 million, 
	expected to be 7 million in 5 years).  Size of a record is about 
	500 to 700 bytes.

Fit on:
	Two 8250's, clustered with an HSC50 and an SA482 (SA482 is four
	RA82's). Addition of more disk is already being accepted.
        16MB is standard memory for the 8250. 

-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  

Questions are:
	1a) Will the eight oracle users fit with 3.5 Million records?
	1b) Would they fit with 7.0 Million?
	2) If not, what changes should be made to the configuration?
	3) How much growth does this (or another) configuration have?

Some things that concern me are: what clustering concerns, such as record
locking across the nodes impact this?  If this the 2-8250's should be replaced
by one machine should it be the 8530 for the VUPS or the 8550 for its I/O
gains?

For reasons that must stay within the group I'm working with, I am unable to
contact Oracle on this one.  Please keep this trust and do not contact Oracle
for me. 

If you feel discussing this one over the phone is better, I'm at DTN:
252-7109.  However, everyone should benefit from the results, so I'll enter
these, if a phone answer is obtained.  Time is of the essence on this one. 

Michael Floeser
Sales Support     <--- this is why its a time crunch.
T.RTitleUserPersonal
Name
DateLines
90.1One CaveatAUNTB::BOOTHA career of MISunderstandingFri Mar 11 1988 23:185
    One thing. It will benefit you to size this for one machine, rather
    than any VAXcluster system as Oracle has no AI journaling capability
    in a VAXcluster configuration, and hence no automatic recovery.
    
    ---- Michael Booth