| 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 am currently involved with a bank in the UK, who need a 'best guess'
at future processing requirements for the comming year. One system
in the cluster uses ingres running a number of applications. I know
nothing about Ingres, but what I was wondering was if somebody out
there had a very basic chart describing performance of ingres vs
machine type , for example,
machine type maximum ingres users memory needed
x y z
This whole exercise is very 'finger in the air' - but any info would
be more than i've got now.
Cheers
David
PS. They are currently running on an 8550 which is about 85% used.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 257.1 | Ingress the dog | MEO78B::RING | Thu Dec 01 1988 23:45 | 13 | |
General ROT (Rule of Thumb) would be about 4 developers per VUP
(VAX Unit of Performance) and about 6-8 end user per VUP depending
on type of usage and optimization of database/application. The major
problem is that V5 of ingress does not use dual processors very
well or SMP at all, therfore to drive a 30 user application maintaining
reasonable response time you would need top of a 6220 or bottom of
6230. Ingress will tell you this is comparable with Rdb/VMS and
this is really ROT (and I don't mean Rule of Thumb).
Hope this has been of some help.
Grantley
| |||||
| 257.2 | Food for ROT ?? | CSOA1::CARLOTTI | OLTP is my life! | Fri Dec 02 1988 15:29 | 7 |
>>>General ROT (Rule of Thumb) would be about 4 developers per VUP... Should we keep this in mind when selling Ingres tools layered on top of Rdb? Rick C | |||||
| 257.3 | Can we displace INGRES? | BROKE::DREYFUS | Fri Dec 02 1988 18:40 | 34 | |
RE .0: What are the chances of displacing INGRES as the DBMS with Rdb? Application migration should be easy with the INGRES tools for Rdb product. Those applications that use 3GL with SQL could benefit from ACMS to achieve higher user numbers per VUP. Those applications and reports that use INGRES' form tools should move over quite easily. Rdb has many advantages over INGRES from a DBMS point of view. The great thing about the INGRES for Rdb announcement is that it allows customers to take advantage of our database while taking advantage of INGRES' tools and portability. RE .2: The answer depends upon the application and the implementation timeline. The current version of the gateway will have performance limitations that should go away with version 6.0 of the INGRES gateways (the current version is 5.0). Sell version 5.0 of the gateways for functionality, portability, application migration, etc. Because of the higher speed of Rdb, more users should be supportable with the 6.0 gateway on Rdb than INGRES tools on INGRES. This, of course, is just an educated guess. We don't know the performance of INGRES DBMS 6.0 or the performance of the gateway on Rdb compared to the INGRES tools against the INGRES DBMS. Most testing uses 3GL code where we expect to outperform all competitors. Hope this helps. --david | |||||