| 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'm musing a question for an Australian bid (probably not the only one,
but that's distribution lists for you). Why would we sell ACMS
with Ingres - what benefit for the customer?
Clearly for Rdb/VMS we require ACMS, but this is less evident for
Ingres. Any experience anyone?
Some of the reasons I might give :
- Performance (bearing in mind we're looking at 15 TPS)
. no overhead of process/image startup
for Ingres client proceses.
- Ease of Management
. ACMS/STOP/START application
cancel user
- clearly managed user population
. Disable/enable tasks
. ACMS/REPLACE server for bugs
- Ease/quality of development
. once learnt, coding very straightforward,
automisation of code blocks possible
. modularistaion of code enforced
- Ease of maintenance
. structured format leads to easy application
maintenance
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 857.1 | How about database threads | TRCO01::MCMULLEN | Ken McMullen | Tue Feb 05 1991 14:43 | 17 |
Rob,
One of the may reasons, no matter what database you are using is the
number of concurrent database threads that must be managed by the
datbase manager. The more users, usually mean the more locks. ACMS
servers can drastically reduce the number of database locks, yet
maintain a high concurrency of users with a good response time.
Other things you may want to check with Ingres or other people are:
What are the largest number of concurrent users they support using
their 4GL tools or through 3GLs? Get references....all vendors say
they can do it.
Find some current ACMS/Ingres references.
Ken
| |||||
| 857.2 | CIMNET::BOURDEAU | Rich Bourdeau CIM Product Marketing | Tue Feb 05 1991 20:28 | 17 | |
In addition...
A client-server database like Ingres lets you break your application
into two pieces, The application and the database server. A TP
monitor like ACMS lets you split the application anywhere you choose.
This capability lets you divide components of your application across
systems suited for that problem.
ACMS also provides a multi-threaded front-end process which controls
manu user process. This capability reduces the memory required to
support large number of users each with their own process.
ACMS also provides other features like security and queueing not
available with a client-server database.
Client-server is only one feature that Ingres and ACMS have in common
and even then the functionality of that feature is not identical.
| |||||