Venu, I would open the variable WPIDLE<LBUG> and watch that variable change on for the station with the large graphic with trends. Also depending on the source station(s) for the C:B.P you might run into trouble from the CP's before the FoxView station. For FV 9 on IA V7 on Microsoft based stations we had large graphics with 12 trends (3 * 4) and it would work fine but it would seem to bog down (Idle <85) when the connections (over 400) all came from the same CP60. So there are a lot of variables involved in your question but if idle is < 85 operators seem to think the station is slow. Terry > From: Shaun.Goldie@xxxxxxxxxxxxxxxxxx > To: foxboro@xxxxxxxxxxxxx > Date: Mon, 22 Nov 2010 14:58:22 +1300 > Subject: Re: [foxboro] trends > > unix FV9.0.1 we experienced FoxView exits when trying to use 12 of the small > trends on a graphic so we gave up, configuring 3 trends with 4 variables was > fine > Shaun > > -----Original Message----- > From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On > Behalf Of Venu Navuluri > Sent: Monday, 22 November 2010 13:53 > To: foxboro@xxxxxxxxxxxxx > Subject: [foxboro] trends > > Hello All, > what is the limit to the number of trends that can be embedded > on the graphic before the processor performance slows down , in other words > if i have a need to show 13 trends for 13 measure parameters apart from > others points on the graphic. Did any one experience slow processor > performance trending on the assigned points. > Regards > > Venu > > > > > _______________________________________________________________________ > 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 > > > > > NOTICE - This message and any attached files may contain information that is > confidential, legally privileged or proprietary. It is intended only for use > by the intended recipient. If you are not the intended recipient or the > person responsible for delivering the message to the intended recipient, be > advised that you have received this message in error. Any dissemination, > copying, use or re-transmission of this message or attachment, or the > disclosure of any information therein, is strictly forbidden. BlueScope Steel > Limited does not represent or guarantee that this message or attachment is > free of errors, virus or interference. > > If you have received this message in error please notify the sender > immediately and delete the message. Any views expressed in this email are not > necessarily the views of BlueScope Steel Limited. > > > _______________________________________________________________________ > 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 > _______________________________________________________________________ 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