| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
From the DECmcc update training I got the message that
a DECmcc station should be
DECstation 2000 model 240 / 48+ MB memory.
VAXstation 400 model 60 / 64+ MB memory.
I work now on that DECstation model but am still not satisfied with the
response times. Because I have not made a deep analysis of the
response times I would like to hear what I can expect in an optimum
case. My concern is to manage a DECnet/OSI pure phase V network at a PTT
site. Is there any difference between those 2 Stations ?
I take the following as reference:
When clicking on an PhaseV icon, how fast should I expect to have the
first entity level expansion to appear on the screen.
Assume I did it already once (to build up the iconic map PM cache).
I would appreciate comments on this kind of performance.
Regards,
Dominique.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3473.1 | Performance again | ZUREDU::MISERRA | Mon Aug 17 1992 09:07 | 14 | |
Hi folks,
this would be of interest to me as well.
I have V1.2 running on a DS 5000-200 with 24MB and RZ56 where it takes
me about 4 min to get the module entities display of a PhV node entity after
double-clicking.
on a VS3100 M38 with 16 MB and working set quota=2048, ws extent=8000
it only (?) takes 3 min.
Any hints what I could do to improve the response times ?
Thanks for any answer,
Klaus
| |||||
| 3473.2 | More memory | RACER::dave | Ahh, but fortunately, I have the key to escape reality. | Mon Aug 17 1992 11:00 | 16 |
In both cases, the systems do not meet the minimum supported configuration (according to the SPD) Also, you do not indicate if it is for the FIRST "look into", or later. The startup overhead for the first one on ultrix includes starting the process the AM runs in, along with loading the (large number) of megabytes of code that are build into the image. Ultrix does not have shared memory like VMS, and the kernel must be build into each AM. In both cases, you should double the amount of memory to reach the minimum supported. 48Meg for Ultrix and 32Meg for VMS. Also, your ws_extent is a little small for reasonable performance. On my 3100 with 16 meg, I have a ws_extent of 20480 pages, and it helps quite a bit. Of course, with such small memory systems, you need to tune really well to free up that much space. | |||||