Conference ilbbak::us_sales_service

55.0. "Network and application responsiveness" by SISDA::CHERNACK (I/O Everybody) Sat Dec 21 1991 06:25

    
    re. 53.2.... (some text deleted)
    
Note 53.2                        Why so quiet??                           2 of 4
MRKTNG::MOLINE                                       26 lines  20-DEC-1991 09:20
                 -< Commitment, Add-Value, Responsiveness ... >-
    
>   One other thing that should be investigated is the responsiveness of
>   the network connection from the field offices. One of the fastest ways
>   to discourage participation is to have long delays between keystrokes.
>   The sales reps and support people cannot wait for 30-second response times.
    
    
    Help!  We haven't heard any cries of anquish regarding responsiveness
    in this conference or the ACCESS conference.  We did a Response Time
    study at the beginning of 1990 to determine ACCESS (VTX) responsiveness
    and concluded that 63% of the time there was better than 5 second
    response time from the time it takes after pressing the carriage return
    to when the first menu of an infobase is returned.  85% of the time it
    was better than 8 seconds.
    
    The Account Workbench is currently being improved, stablilized and
    performance tuned due to known throughput problems.
    
    Our Corporate Network Support team believes the bandwidth for our
    backbone network is adequate and that they have projected enough
    capacity for the future.
    
    HOWEVER, if that is not the case.... if you have some war-stories (good
    and bad).... if you sit at the end of a network segment.... if you only
    use WATN (formerly TSN).... if you only have 1200 baud access.... if
    you need more VUPS... if you <fill in the blanks>, PLEASE LET US KNOW.
    
    'Tis the squeaky wheel that tends to get oiled first!