Re: [foxboro] Remote display call up speed

LI= Lan Interface module
Yes please do a glof on C:B.P

e.g.  /op/fox/bin/tools/glof UC001:STATION.TOTMEM
to get at the station block of CP UC0001

Warren




>From: "Guzenske, Sue (USBORAX)" <Sue.Guzenske@xxxxxxxxx>
>Reply-To: foxboro@xxxxxxxxxxxxx
>To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
>Subject: Re: [foxboro] Remote display call up speed
>Date: Thu, 10 Jan 2002 22:44:58 -0000
>MIME-Version: 1.0
>Received: from [168.215.193.75] by hotmail.com (3.2) with ESMTP id 
>MHotMailBE07662E003C400438CCA8D7C14B0FA40; Thu, 10 Jan 2002 14:52:31 -0800
>Received: from turing.(none) (localhost [127.0.0.1])by turing.freelists.org 
>(FreeLists Mail Multiplex) with ESMTPid AD760844BD; Thu, 10 Jan 2002 
>17:51:55 -0500 (EST)
>Received: with LISTAR (v1.0.0; list foxboro); Thu, 10 Jan 2002 17:50:45 
>-0500 (EST)
>Received: from old-n2.infonet.com (old-n2-130.infonet.com 
>[192.157.130.138])by turing.freelists.org (FreeLists Mail Multiplex) with 
>ESMTP id 05B65842B1for <foxboro@xxxxxxxxxxxxx>; Thu, 10 Jan 2002 17:50:44 
>-0500 (EST)
>Received: from infexch01.infonet.com (infexch01 [192.92.62.83]) by 
>old-n2.infonet.com (8.11.3/8.6.12) with ESMTP id g0AMmun04126 for 
><foxboro@xxxxxxxxxxxxx>; Thu, 10 Jan 2002 22:48:56 GMT
>Received: by INFEXCH01 with Internet Mail Service (5.5.2653.19)id 
><CVDTR2KQ>; Thu, 10 Jan 2002 22:51:09 -0000
>From foxboro-bounce@xxxxxxxxxxxxx Thu, 10 Jan 2002 14:54:32 -0800
>Delivered-To: foxboro@xxxxxxxxxxxxx
>Message-ID: <0969D9827D31D211B09900104B9BC118012A9339@boraxexch02>
>X-Mailer: Internet Mail Service (5.5.2653.19)
>X-archive-position: 506
>X-listar-version: Listar v1.0.0
>Sender: foxboro-bounce@xxxxxxxxxxxxx
>Errors-To: foxboro-bounce@xxxxxxxxxxxxx
>X-original-sender: Sue.Guzenske@xxxxxxxxx
>Precedence: normal
>X-list: foxboro
>
>
>Ron:  Here are the vmstat 5 5.
>
>procs     memory            page            disk          faults      cpu
>  r b w   swap  free  re  mf pi po fr de sr f0 m0 m1 m2   in   sy   cs us 
>sy
>id
>  0 0 0  12532  6352   0   8  0  0  0  0  0  0  0  0  0   76  658  275  2  
>2
>96
>  0 0 0 179488  3804   0   2  0  0  0  0  0  0  0  0  0  107  992  287  4  
>3
>93
>  0 0 0 179488  3804   0   0  0  0  0  0  0  0  0  0  0   74  673  283  2  
>1
>96
>  0 0 0 179488  3804   0   0  0  0  0  0  0  0  0  0  0   98  938  283  4  
>2
>93
>  0 0 0 179488  3804   0   0  0  0  0  0  0  0  0  0  0   82  848  285  3  
>2
>95
>The above is box A, which supports 5 DMs quickly.
>
>procs     memory            page            disk          faults      cpu
>  r b w   swap  free  re  mf pi po fr de sr f0 m0 m1 m2   in   sy   cs us 
>sy
>id
>  0 0 0   4408  2680   0   5  0  1  1  0  0  0  0  0  0   49  447  270  1  
>1
>98
>  0 0 0 155068  2080   0   2  0  0  0  0  0  0  0  0  0   58  446  274  0  
>1
>99
>  0 0 0 155068  2088   0   0  0  3  3  0  0  0  0  0  0   55  438  272  0  
>0
>99
>  0 0 0 155068  2096   0   0  0  0  0  0  0  0  0  0  0   52  421  275  0  
>0
>99
>  0 0 0 155068  2096   0   0  0  0  0  0  0  0  0  0  0   51  444  273  1  
>1
>99
>This is box B, which supports one or two DMs slowly.   What does the swap
>and free memory say about these boxes?
>
>All of the remote DMs are View-Only.  Box B has one remote DM dedicated to 
>a
>particular PC, all others are for whatever PC gets there first.
>
>.....
>
>Items from Warren Brown's note:
>"Another thing to check is the network topology. You don't mention if one 
>of
>the AW's is behind
>an LI ?" ... ( Sorry, what's an LI? )
>
>"One interesting thing to test is to do a 'glof'
>/opt/fox/bin/tools/glof Control_Point  (one that is on the display)
>on both AW's and see if both take approximately the same time to respond
>?"... ( Both boxes respond very quickly finding letterbugs and process
>locations;  I'm not sure how to ask for a "Control Point"  do you mean
>Compound:Block.Parameter ?)
>
>Thank you again,
>Sue
>-----Original Message-----
>From: Deen, Ron [mailto:rdeen@xxxxxxxxxxx]
>Sent: Thursday, January 10, 2002 2:36 AM
>To: foxboro@xxxxxxxxxxxxx
>Subject: Re: [foxboro] Remote display call up speed
>
>
>
>Can you list the /usr/fox/customer/hi/dmcfg file(s)?
>
>Can be that not all DM are "view-only" which are by nature slower than
>"operator class" dm's. I have see nproblems with this in the past with
>symptoms similar to what you describe.
>
>Idle time is not the only important value. available swapspace etc can =
>be of
>importance. Can you provide a few lines of vmstat 5 from both systems =
>maybe?
>
>Regards
>
>Ron Deen
>Senior System Service Specialist
>Invensys Systems N.V.
>Baarnsche dijk 10   P.O. Box 146   3740 AC Baarn   The Netherlands
>T: +31 (0)35 54 84 233   F: +31 (0)35 54 84 175 =20
>Ron.Deen@xxxxxxxxxxxx   www.invensys-systems.nl
>
>
>A P V  =B7  F o x b o r o  =B7  S i m S c i  =B7  T r i c o n e x  =B7  =
>W o n d e r
>w a r e
>
>
>
>
>-----Original Message-----
>From: Guzenske, Sue (USBORAX) [mailto:Sue.Guzenske@xxxxxxxxx]
>Sent: Wednesday, January 09, 2002 10:27 PM
>To: 'foxboro@xxxxxxxxxxxxx'
>Subject: [foxboro] Remote display call up speed
>
>
>
>I have two AW51B units, both at 170 mHz, version 4.3, who support old =
>style
>display managers using Exceed to supply view-only displays to PCs on =
>our
>plant network.
>
>Box A supports 5 remote DMs and has a display call up time of about 1 =
>second
>on a PC.  This box had 128 meg of RAM. Vmstat usually shows 90-95% idle
>time.
>
>Box B supports 1 or 2 remote DMs and can take up to 5 seconds to brings =
>up a
>display on a PC.  This box has 96 meg of RAM.  Vmstat usually shows =
>95-99%
>idle time.
>
>Taking the le1 (2nd Ethernet connection)down and then putting it back =
>on
>makes no change in the display call up speed.  Neither box seems to =
>have any
>time hogging processes running when ps -eaf is checked.=20
>
>What else can I check?  I'd like to get box B to perform like box A.
>
>Thank you for your help.
>
>Sue Guzenske
>U.S. Borax Inc.
>=20
>=20
>___________________________________________________________________
>This list is neither sponsored nor endorsed by The Foxboro Company.
>Use the information obtained here at your own risk. For disclaimer,
>see http://www.thecassandraproject.org/disclaimer.html#maillist
>
>list info:   http://www.freelists.org/list/foxboro
>subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
>unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>
>
>___________________________________________________________________
>This list is neither sponsored nor endorsed by The Foxboro Company.
>Use the information obtained here at your own risk. For disclaimer,
>see http://www.thecassandraproject.org/disclaimer.html#maillist
>
>list info:   http://www.freelists.org/list/foxboro
>subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
>___________________________________________________________________
>This list is neither sponsored nor endorsed by The Foxboro Company.
>Use the information obtained here at your own risk. For disclaimer,
>see http://www.thecassandraproject.org/disclaimer.html#maillist
>
>list info:   http://www.freelists.org/list/foxboro
>subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>




_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

 
 
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: