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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

535.0. "Horrible performance on LAVc" by CSC32::G_JOHNSON (Just a nickle's worth of dreams) Tue Apr 04 1989 14:34

    Hi,
    
    	We have had at least two different customers call in with a
    similar problem dealing with performance in a LAVc environment.
    Here are the symptoms.  Any hints as where to look would be much
    appreciated.
    
    	Running in a LAVc environment on a WS2000 with 16 MB, over half
    free, on both the boot and local node.  Using local page and swap
    files.  When starting up a file view, decterm, or other OTB app,
    it takes between 1 and 2 MINUTES for the window to appear.  When
    brining up a dialog box or a DCL command box, etc, it takes 30-40
    seconds.
    
    	WS quotas on both systems are high as are the PQL's on both
    systems.
    
    	On the boot node, they are running VWS, but when they boot the
    local node, they are using a different .PAR file with the DECwindows
    sysgen params in them.
    
    	I have run out of ideas on things to look for.  Any one seen
    this happen before, or have any ideas what else to look at?  Thanks
    for any and all hints!
    
    Greg...

T.RTitleUserPersonal
Name
DateLines
535.1Couple more itemsCSC32::G_JOHNSONJust a nickle's worth of dreamsTue Apr 04 1989 15:007
    A couple of addendums.  First of all, the apps are being run on
    the boot node, not locally.  Secondly, this is not, I belive, the
    pipe line problem discussed in 428, as their pipeline quota is only
    at 15,000 on both nodes.
    
    Greg...

535.2Need more infoPOOL::BUFORDOhayo, y'all!Wed Apr 05 1989 10:3513
    I may be showing my lack of knowlege regarding workstation platforms,
    but here goes:  what's a "WS2000"???  If you meant "V" instead of "W"
    (as in a VaxStation 2000) then did you mean 14 MB instead of 16?
    
    Try this as a first step, use MONITOR or SPM on both nodes.  The
    boot node will probably be more interesting since that is where the
    application is accessing the disk(s).  From your note, you don't think
    it is a memory saturation problem.  That leaves disk I/O, CPU, and 
    network I/O...
    
    
    John B.

535.3HOOKER::JACKMarty JackWed Apr 05 1989 10:544
    Slight digression:  16MB memory boards for VS2000s have been available
    from Clearpoint for years.  We tend to forget that customers can
    buy equipment from anyone ...

535.4Need more info on LAVCHYEND::JBOWKERJoe, KB1GPWed Apr 05 1989 14:219
    A few more questions:
    
    What does your LAVc Configuraton look like? (ie how many satellites?, what
    does network path look like?) 
    
    Have you looked at any of the NCP error counters?
    
    Joe

535.5Final outcome?POOL::CAFARELLATue Apr 25 1989 15:3311
    
    Did this problem ever get resolved?  Is it something the rest of us
    should know about?
    
    Thanks.
    
    
    Tom Cafarella