| 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 |
We need to size an ORACLE production development environment. Our
customer intends to have a 700Mb production database. Neither the
customer nor us has a detailed design spec about how many files,
the number of keys per file or how many quries or updates will be
done.... so it goes...
What we are looking for is estimates concerning VAX configurations
for the following:
o 50 concurrent users doing inquiry only.
o 30 applications developers - working under SQL forms plus and
some C.
Given the meager information provided , does anyone out there have
a feel for how much CPU these dear folks need??
Can anyone point us to a source of Oracle sizing information??
(person or documentation)
Thanks Ed G.
(dtn 333-6466)
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 16.1 | HAVE TO HAVE more information | BANZAI::CAMERON | Wed Jul 15 1987 16:30 | 7 | |
Need more information. TPS, I/Os per sec, Reads/writes/updates.
Any other products like an active DECnet, VAXset, ...
I suggest that you call the ORACLE sales rep and work with them.
It would be good to post their replys.
| |||||
| 16.2 | ORACLE Performance? | ODIXIE::NUHFER | Thu Aug 06 1987 23:31 | 8 | |
I would really like some definitive information too. I called our
'local' rep and tried to get something regarding performance. All
he could offer was a relative benchmark that they had done against
Ingress. He would not give any TPS (even a ROM).
I am currently hearing that the transaction rate is no better than
Rdb 3-5 TPS. This is only rumor and I would like for someone to
confirm or deny even this.
| |||||
| 16.3 | Not much but probably bad | USHS01::SPARKS | Wed Sep 02 1987 22:57 | 23 | |
I can give you some information about the last installation I was
at. They had ORACLE with database size approx 700 mg. The system
was basically query with new data being inserted by batch processes
during off hours. First the BI for the database had
to be between
1/4 to 1/2 the size of the database and was on a separate
drive from the database which was spread across several drives.
The database had about 10 large tables with between
200,000 to 400,000 rows and about 60 supporting tables with between
1000 - 20000 rows. The Machine we were using was a 8600 in a cluster
environment. It had 80 meg memory and used hsc50 cont. with 14
RA-81 drives. They were also running a dbms-32 application on the
same machine. There was about 35 oracle users and about 20 dbms-32
users on during the day. An interesting note was that the two systems
co-existed very well. If the DBMS-32 database was down the oracle
users didn't notice much difference and visa versa. We tried to
move the Oracle database to a 780 with 12 meg on the same cluster
and with 12 oracle users the preformance was deemed unacceptable
(this was the F A S T version 5.1 too). So with the little
information that you have I would have to say with my experience
would be as big as they can get and no less than an 8600. Another
rule of thumb is to take what ORACLE tells you and double it and
add some for the real world element. Good Luck!
| |||||