Re: [foxboro] Splitting one node increases the display call-up time?
- From: "Ron Schafer" <rschafer@xxxxxxxxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 13 Feb 2007 08:06:10 -0500
I ran into a similar situation where all stations were having call up
delays and it turned out to be a ver 6.1.x issue where the server70
(also our historian) was running out of free Om lists. When we would
reboot this station everything cleared up and it wouldn't re-appear for
a couple of weeks. We ended up finding show_params gave us the
indication that the OM_lists (I believe) was out of free lists. A reboot
would fix it, but a revision level upgrade solved the problem.
Something to take a look at especially if your running any AW70's with
internal CP's (IO gates) or Server70's.
Ron Schafer
Whitebirch Paper
Bear Island Division
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Dimitris Legakis
Sent: Tuesday, February 13, 2007 4:23 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Splitting one node increases the display call-up
time?
Regarding the questions you had:
1. The CPs I am using are CP60
2. The speed is always slow on the same displays. However, in several=20
workstations it seems that the display appears really fast! for example
a=20
page that takes 3 sec on other workstations, needs 1,5 on the specific
one!=20
the difference is that the fast one is DELL Optiplex270 and the slow are
DELL Optiplex260. Could the workstation's characteristics (e.g. Memory,=20
Processor etc)) make the difference on the display call-up time?
3. Regarding the overruns and the CP loads, I will check tomorrow and
see=20
what happens when I call up a heavy page.
Thank you all for your suggestions.
Dimitris
>From: "Johnson, Alex P (IPS)" <alex.johnson@xxxxxxxxxxxxxxxx>
>Reply-To: foxboro@xxxxxxxxxxxxx
>To: <foxboro@xxxxxxxxxxxxx>
>Subject: Re: [foxboro] Splitting one node increases the display call-up
>time?
>Date: Fri, 9 Feb 2007 10:28:11 -0500
>
>It looks like the limitation is the CP. Especially if they are older
>models for whom 80% loading is above our recommended levels.
>
>
>What type of CPs are they?
>
>
>
>You might want to watch the loading display while you call up a slow
>display on another FV/DM. I suspect you'll see it peg out.
>
>
>
>Also, what do your overrun counters look like on these machines?
>
>
>
>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
>
>
>
>-----Original Message-----
>From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
>On Behalf Of Dimitris Legakis
>Sent: Friday, February 09, 2007 10:01 AM
>To: foxboro@xxxxxxxxxxxxx
>Subject: Re: [foxboro] Splitting one node increases the display call-up
>time?
>
>
>
>Acually there is no unresolved links in any of my pages. I have checked
>that
>
>already.
>
>Regarding the CP loads, they are:
>
>CP1: 83.4%
>
>CP2: 87.2%
>
>CP3: 68,4%
>
>CP4: 87.4%
>
>CP5: 86.2%
>
>CP6: 42.6%
>
>CP7: 78.8%
>
>CP8: 78.4%
>
>CP9: 25.2%
>
>
>
>I am also using FOXVIEW for the display of the pages.
>
>
>
>I have tried to symplify the symbols that were in use in all pages and
>the
>
>speed has been improved, but is still slower than the desired. I also
>have
>
>the impression that sometimes the static objects appear first, some
>dynamic
>
>object appear a little time later and the rest in the end.
>
>regards,
>
>
>
>Dimitris
>
>
>
>
>
> >From: "Johnson, Alex P (IPS)" <alex.johnson@xxxxxxxxxxxxxxxx>
>
> >Reply-To: foxboro@xxxxxxxxxxxxx
>
> >To: <foxboro@xxxxxxxxxxxxx>
>
> >Subject: Re: [foxboro] Splitting one node increases the display
call-up
>
>
> >time?
>
> >Date: Fri, 9 Feb 2007 08:16:38 -0500
>
> >
>
> >I seriously doubt that your issues are related to the speed of the
>
> >network.
>
> >
>
> >It is far more likely that the CP's are heavily loaded and/or there
are
>
> >missing tags on the displays. To check the former, use the Station
>
> >block. To check the latter use dedit or d_edit (depending on DM or
FV)
>
> >and run the validation check.
>
> >
>
> >Regards,
>
> >=3D20
>
> >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
>
> >
>
> >-----Original Message-----
>
> >From: foxboro-bounce@xxxxxxxxxxxxx
>[mailto:foxboro-bounce@xxxxxxxxxxxxx]
>
> >On Behalf Of Dimitris Legakis
>
> >Sent: Friday, February 09, 2007 4:14 AM
>
> >To: foxboro@xxxxxxxxxxxxx
>
> >Subject: [foxboro] Splitting one node increases the display call-up
>
> >time?
>
> >
>
> >Hello all,
>
> >
>
> >I have a configuration with 9 CP60s in one Node of two NCNIs that
>are=3D20
>
> >conncted to two Switches were the Workstatins are linked (through
>
> >RCNIs).
>
> >
>
> >The idea is to split the node into three separate nodes. i.e. use
>three=3D20
>
> >couples of NCNIs, one couple for each three CPs and connect them
>
> >separately=3D20
>
> >on the two switches. As a result, this should share the traffic
amoung
>
> >three=3D20
>
> >different paths. The result we are expecting is a Faster response on
>the
>
> >
>
> >graphic displays. Bear in mind that up to now some displays require
>more
>
> >
>
> >than 3-4 seconds to refresh all their data.
>
> >
>
> >Do you think that this will improve the display call up times? Has
>
> >anyone=3D20
>
> >found a way to improve the display call-up times? any suggestions?
>
> >
>
> >thank you all in advance
>
> >regards,
>
> >Dimitris
>
> >
>
> >_________________________________________________________________
>
> >Express yourself instantly with MSN Messenger! Download today it's
>FREE!
>
> >
>
> >http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
> >
>
> >=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:
>mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
>
> >to unsubscribe:
>mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
>
> >=3D20
>
> >
>
> >
>
> >
>
> >Confidentiality Notice: =3D0AThe information contained in this
electronic
>m=3D
>
> >essage and any attachment(s) to this message are intended for the
>exclusi=3D
>
> >ve use of the recipient(s) and may contain confidential, privileged
or
>pr=3D
>
> >oprietary information. If you are not the intended recipient, please
>noti=3D
>
> >fy the sender immediately, delete all copies of this message and any
>atta=3D
>
> >chment(s). Any other use of the E-Mail by you is prohibited.=3D0A
>
> >
>
> >
>
> >
>
>
>_______________________________________________________________________
>
> >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=3Djoin
>
> >to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>
> >
>
>
>
>_________________________________________________________________
>
>Express yourself instantly with MSN Messenger! Download today it's
FREE!
>
>
>http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
>
>
>
>
>
>_______________________________________________________________________
>
>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=3Djoin
>
>to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>
>
>
>
>
>
>
>Confidentiality Notice:
>The information contained in this electronic message and any
attachment(s)=20
>to this message are intended for the exclusive use of the recipient(s)
and=20
>may contain confidential, privileged or proprietary information. If you
are=20
>not the intended recipient, please notify the sender immediately,
delete=20
>all copies of this message and any attachment(s). Any other use of the=20
>E-Mail by you is prohibited.
>
>
>
>
>Confidentiality Notice:
>The information contained in this electronic message and any
attachment(s)=20
>to this message are intended for the exclusive use of the recipient(s)
and=20
>may contain confidential, privileged or proprietary information. If you
are=20
>not the intended recipient, please notify the sender immediately,
delete=20
>all copies of this message and any attachment(s). Any other use of the=20
>E-Mail by you is prohibited.
>
>
>
>
>_______________________________________________________________________
>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=3Djoin
>to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
=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:
