| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4795.1 | | TOOK::MCPHERSON | pre-retinal integration | Thu Apr 01 1993 11:15 | 12 |
| It varies depending on the MMs invoked by the rule.
For example: if you create an alarm rule on a STATISTIC, then you
(transparently) use the services of the
1. the PA FM (gets called once for each statistic)
2. the AM called by the PA FM (gets called twice for ea statistic)
Different MMs use different amounts of memory.
If you can give a more *specific* example, then it's a fairly straightforward
exercise to empirically determine how much memory each rule consumes.
/doug
|
| 4795.2 | | HKGACT::SUSANCHAN | | Thu Apr 01 1993 21:36 | 14 |
| If there are so many variants on the memory usage for different MM,
why it isn't documented? At least a guideline?!
This is being asked by customer. In the manual, it only recommended a
separate account for ALARM enabling, but it doesn't give any idea of what
the process quota for the account. There is a very high chance of system
hang/crash because of insufficient resource (which I had experience before
and I have to perform system monitoring to find out ALARMS eat up a lot
of memory).
It is wiser to have the user to set up a workable environment at the very
beginning.
/Susan
|
| 4795.3 | where would you document it | TOOK::CALLANDER | MCC = My Constant Companion | Tue Apr 27 1993 15:19 | 10 |
| where and how do you think it should be documented?
I am not be sarcastic, I really am interested in knowing how would you
want to see it documented. End user documentation? a quick cheat sheet
for the support center? A procedure you run and it gives you a hit
about what it thinks you might need? The alarm manager includes an
estimate in the templates?
other ideas?
|
| 4795.4 | TRy running the config tool | RACER::dave | Ahh, but fortunately, I have the key to escape reality. | Tue Apr 27 1993 17:53 | 4 |
| You could also run the configuration tool and see what it says the requirements
are. Its real close on lots of things....
See the MCC-TOOLS conference
|