| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2872.1 | IMPM startup and look-into | ICS::WOODCOCK | | Thu Apr 30 1992 12:34 | 25 |
| >What I'd like to hear from the general DECmcc internal field test community is:
> - areas of DECmcc performance that need investigation
> preferably things that are very end-user visible
> (i.e. potential big wins)
IMPM performance is questionable. This includes map startup and looking
into domains. At startup MCC IMPM consumes every available ounce of CPU.
This takes about 3 minutes for our stuff and the IMPM brings the CPU to 100%
for approximately this entire time. FWIW this is an 8810 *not* a workstation,
our test workstation can take several more minutes to come up.
Generally speaking, it takes too long to look into domains and entities
(although for entities I don't know how much the network plays). But even for
local entities on the LAN it seems to take too long. Both of these problems
are obviously quite visible to the customer.
> - hints or ideas on what might be causing these performance problems,
> (to help focus and guide our efforts)
Sorry, none.
best regards,
brad...
|
| 2872.2 | More work on Memory Management | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Fri May 01 1992 02:01 | 25 |
| The decision to include global alarm rules has had the added value of
reducing precious memory consumption (~120K bytes per alarm rule).
This is beside the fact that global alarms make managing the network
much easier.
In addition, there is less CPU overhead expended. I must say, this was
one of the SMARTEST moves you could have made. I can now do with 15
rules what had been taking me 150+ (and would have easily grown to
800+ with enough CPU & memory to allow for the growth.) OUTSTANDINGLY
EXCELLENT JOB!! Keep working to improve this capability.
My suggestions for improved performance also lie in the area of reading
in MAP files (e.g., looking into domains). Perhaps some automatic
means of keeping the map files contiguous on disk (or contiguous/best
try), or making documented suggestions that all MCC files be on LOCAL
disks as opposed to MSCP-served across the network.
Anything that can improve DNS access would be a plus.
Slow performance is my customer's biggest complaint with DECmcc. V1.1
with 40 alarms enabled (5 min poll) rendered one VAXstation 3100/38-SPX
unusable. V1.2 should prove much better, but still has a way to go.
You're definitely headed in the right direction, though.
8~) -Dan
|
| 2872.3 | Slow IMPM on ULTRIX | DOTTY::WITHERELL | | Thu May 07 1992 16:13 | 18 |
| I am running ULTRIX 4.2A on a DECstation 5000 model 240 with 24 MB
memory and the performance of the IMPM is extremely slow. The customer
is about fed up with the product because of this. Double clicking on a
Phase V entity takes about 10 minutes. Other entities are not as slow
but still take several minutes. I notice that the second time you open
the same class of entity, performance is better but not really great.
Listing and opening domains is slow as well.
I am not sure what is causing the problem. I have followed the
configuration guidelines in the installation guide. I don't hear a lot
of disk activity (indicating paging and swapping) when these operations
are taking place.
I really hope performance can be improved. I have been telling the
customer that it's field test software and this problem will probably be
fixed before it's released.
Good luck.
|