[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

2261.0. "Historical Datarecording performance" by ZUR01::SCHNEIDERR () Tue Feb 04 1992 05:48

Hello,

One of our DECmcc customers told me about a situation:

He records some date. About 15 circuits (Synch ports on DEMSAs).
		      Counter polls each 15 min, characteristic poll once a day

		      3 lines (also on DEMSAs)
		      Counter polls each 15 min, characteristic poll once a day

He told that everything is working, but the consumption of CPU time of the
historian process is growing up every day. After 2-3 weeks the consumtion is about
30-50% CPU time.

Is this normal. Funny is that the cpu consumption isn't stabile, it grows up.


Thanks Roland
T.RTitleUserPersonal
Name
DateLines
2261.1additional information requestedTOOK::SHMUYLOVICHTue Feb 04 1992 18:4911
    	We've never seen such behavior of the Historian.

    	Would you, please, give us more information:

    1. What operating system are you running? What version?
    2. What version of MCC?
    3. How did you monitor the "historian process"?
    4. Which process has been monitored?

	Thanks, SAm
2261.2some infos moreZUR01::SCHNEIDERRWed Feb 05 1992 03:2017
Sam,

O.K. I should tell you more about the story. Maybe you noticed, that I entred 
some notes together. All from the same customer. He is one of our major
customers here in Switzerland. He rapported 16 problems in DECmcc. My problem
is, that I can't reproduce nothing from his problems.

He runs BMS V1.1 and VMS V5.4-2.
He made a monitor system and saw the MCC_HISTORIAN_BACHGROUND process using
between 30 - 50% CPU time. He runed 6 processes for 6 domains. He reboots his 
Workstation twice a week, because he has a lot of problems with event handler
and alarms. After 3 or 4 weeks he realiced this effect. Now he stopped the 
Historian. I told him to restart it and have a look to it. In 5 domains he had
actualy no datarecording running. This 5 processes had nearly no CPU consumption.


Thanks Roland
2261.3more information pleaseTOOK::CALLANDERMCC = My Constant CompanionTue Feb 11 1992 11:596
    could you provide some additional information regarding what other mcc
    processes he is running (like rules, or exportings) and what this
    pagefile size (and quota) are.
    
    thanks
    
2261.4I will do itZUR01::SCHNEIDERRWed Feb 12 1992 03:008
Hello,

Thanks for your replies. I will post more infos, if I will have it. The customer
now started historian again. As you can read in .0 we have to wait sone days.
Then I will have a look to the system and post here whats happen.


Thanks regards Roland
2261.5He I am againZUR01::SCHNEIDERRThu Mar 19 1992 09:2216
Hello,

4 weeks ago we started the historian again. Still we record the same datas as 
discribed. We saw that. The customer made a show system every 24 hours and wrote
down the timeconsumption of the historianprozess. This growed up every day. 
Yesterday the historian used close to 5 hours CPU a day. Thats an averadge of 20%
CPU time. The system became slower and slower. He has to wait up to 2 minutes
from click an icon to the action. 
The system is totaly overloaded. As background he runs the background (witch we
stoped now) and about 300 alarms (polling bridges every 5 minutes). The machine 
is a 3100/76 with fully expanded memory. Is it realy normal that the historian
takes so mutch CPU power. The histfile is in the meantime 70mb big. You can't use 
the historian in this circumstances. Whats going on with DECmcc.


Roland
2261.6Stop/StartMAYDAY::ANDRADEThe sentinel (.)(.)Thu Apr 09 1992 11:1312
    Roland, 
    
    If you haven't taken care of this already. The thing to do is to stop
    and start all DECmcc processes before they grab up too much resources. 
    
    I would recomend you stop and start all of them at least once a day.
    You can do this from command procedures, during the night.
    
    *** One thing, I knew DECmcc leaked memory. But this is the first time
    I hear about it "leaking" CPU cycles. (-; 
    
    Gil