| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4208.1 | What are your Working Set parameters ? | ONTIME::BUGSBY::COBB | Writing from ALPHA AXP | Tue Dec 08 1992 07:11 | 30 |
| I had this problem even with 48 meg of memory. I am running it on a
3900, which could be argued as a unsupported BMS platform according to
the SPD. I bumped up the quotas on the account it runs out of and
performance has improved. My quotas are below:
Maxjobs: 0 Fillm: 1000 Bytlm: 100000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 1000 JTquota: 2048
Prclm: 0 DIOlm: 1000 WSdef: 28000
Prio: 4 ASTlm: 1000 WSquo: 30000
Queprio: 0 TQElm: 1000 WSextent: 34000
CPU: (none) Enqlm: 1000 Pgflquo: 150000
The one that made the real difference was the Working set parameters.
Now with 24 meg, you may not be able to go as high as I have it. I
have seen my MCC process grab as much as 30000 of the WSEXTENT. Before
I bumped it up, I would see my MCC process constantly maxed out at
WSEXTENT. That is when I had slow menu pulldown problems. I moved it
up and the problems have gone away.
How many other things do you have going on other than MCC? How many
alarms do you have running? Remote sinks and events turned on? All
of these things take more processing power away from the interface.
With 50 alarms and exporting going on and 5 LTM interfaces running,
performance is not too bad.
Hope this helps,
Bill
|
| 4208.2 | MCC_AUDIT is reasonable | FARMS::LYONS | Ahh, but fortunately, I have the key to escape reality. | Wed Dec 09 1992 20:42 | 14 |
| MCC_AUDIT makes suggestions for REASONABLE performance.
While the SPD does say only 24 Meg is the MINIMUM, please note that it is
the MINIMUM, e.g. the ABSOLUTE MINIMUM, and don't ever configure a system with
that little memory if you expect it to run in a reasonable fashion.
In your base note you said:
a production MCC system should have 32MB of memory
^^^^^^^^^^
Thats the point. In the future, I would not be at all supprised if the numbers
were raised significantly in the SPD, like they were for the EMS kit.
If you want to know what size of memory to have on a system, run the MCC sizer
tool pointed to in the NOTED::MCC-TOOLS conference. It does a reasonable job
for V1.2 based systems.
|
| 4208.3 | Many Thanks | BELFST::ROONEY | Hugh Rooney | Thu Dec 10 1992 05:43 | 18 |
|
re: .1
Thanks for the info Bill, I have tried this approach and the performance has
improved.
re: .2
I would have thought that a minimum configuration was one that did offer
reasonable performance. The system performance is now just about acceptable
after the changes outlined in .1. I would however agree that the 24MB minimum
in the SPD should be reviewed.
Thanks for the pointer to the sizing tool, it is very useful.
hugh
|