Re: [foxboro] Problems with the Process Summary Reporter?
- From: "Doucet, Terrence" <tdoucet@xxxxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 8 Jun 2007 13:09:02 -0400
Virgil,
Remember that the Foxboro system does a "graceful" overrun so when you =
see 66% you need to look to see of the counter ticked over because you =
could be at 132% loading but "gracefully" you go to 66% with one tick =
of the counter.
An overrun does not necessarily mean lost data but rather it could mean =
lost data. No overrunns definitely gives you confidence in no lost data.
Terry
-----Message d'origine-----
De : foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
De la part de Loudermilk, Virgil:
Envoy=E9 : June 8, 2007 7:56 AM
=C0 : foxboro@xxxxxxxxxxxxx
Objet : Re: [foxboro] Problems with the Process Summary Reporter?
Yes, Alex, the problem with the inaccessible CPs is the same when run =
daily, pretty infrequent, maybe 10% of the time. I'll have to get back =
to you on the sporadic missing blocks, since I don't really know yet and =
I will have to watch it closely.
Thanks, I'll keep an eye on the OM loading when it runs. So far I see a =
spike from the normal 2% up to 66% or so for a few seconds on the most =
problematic station, which of course happens to be a Micro I/A. I =
noticed that Micro IA is ominously omitted in the PSR documentation on =
the list of stations that the PSR works with.
I'm about ready to back off the 10 minute frequency I used for testing, =
but it did well.
Incidentally, the whole reason I am working with this is to move the =
reports it to an AW that is not hosting the DMCPlus interface since I =
suspect this is what is causing our intermittent DMC stoppages that =
almost always occur when these reports run. Also incidentally, the =
reports that I'm moving use mostly CPs that were previously on a =
different node than the AW they are running on. I thought the switch =
replacement for the old Carrier Band LAN connection was supposed to make =
the whole thing perform like one node, but it sure seems to me that we =
have performance like we still have two nodes with some kind of lower =
capacity bridge in between.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Johnson, Alex P (IPS)
Sent: Thursday, June 07, 2007 9:01 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Problems with the Process Summary Reporter?
The PSR uses the db_query service to get the data (the same thing =
getpars uses).
If other applications are making similar queries, you might be hitting a =
limit.
As for the run the PSR every 10 minutes idea that seems pretty often.
I'd bet that the designers of the db_query mechanism (a low priority =
task in the CP) were not expecting it to be used quite so often.
Do you have the same problem when it is run less often?
Regards,
Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx
Confidentiality Notice:
The information contained in this electronic message and any
attachment(s) =3D3D
to this message are intended for the exclusive use of the recipient(s) =
and =3D3D may contain confidential, privileged or proprietary =
information. If you are=3D3D not the intended recipient, please notify =
the sender immediately, delete a=3D3D ll copies of this message and any =
attachment(s). Any other use of the E-Mai=3D3D l by you is prohibited.
=3D20
=3D20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process =
Systems (formerly The Foxboro Company). Use the info you obtain here at =
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=3D20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=3D20
=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process =
Systems (formerly The Foxboro Company). Use the info you obtain here at =
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
