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

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

1453.0. "Hubwatch-->Deathwatch ? Performance?" by PTOJJD::DANZAK (Pittsburgher �) Tue Sep 20 1994 11:16

    Can anything be done to fix HUBwatch performance?  If you make an error
    it can be EMBARASSINGLY slow to the point of death (take 2-3 minutes to
    respond!)  I can understand/explain some of the repeater stuff, but
    moving a module to/from segments should NOT take over 10-15 seconds. 
    It REALLY demos bad.  To demo HUBWATCH effectively, you really need to
    understand what to AVOID from a performance point of view.
    
    Are any thoughts being given to some rewrite or revision that would
    perhaps do things more efficiently and fix the performance issues.
    
    Regards,
    j
    ^--who votes to rename HUBWATCH to DEATHWATCH
T.RTitleUserPersonal
Name		DateLines
1453.1SLINK::HOODI'd rather be at the PenobscotTue Sep 20 1994 11:5117
The reason we made HUBwatch so slow is that we like to sit around doing
nothing for most of the day.  Double-click a module, take a coffee break.
Come back, setup a LAN connection, take a long lunch.
Making it faster would make our jobs harder.

Although it might not look like it, each version does get a little faster.  As
new windows are developed, performance innovations are added. We are *trying* 
to improve the overall performance.   Nowadays an important factor 
for each new screen is speed.  Yeah, some things are annoyingly slow (for
us too), but we're trying.  Really.


Tom Hood
DEATHwatch

ps:  There's been no trademark search done for DEATHwatch, so we should
     probably just keep the HUBwatch name for now.
1453.2I understand - just so ya know!PTOJJD::DANZAKPittsburgher �Tue Sep 20 1994 12:4214
    (grin) Sounds just like the field....we don't to much but drink coffee
    either and wait for the orders to come in.....
    
    I understand - just wanted to make you aware that the performance in
    some instances is really an issue (i.e. over 20 seconds to up to 2
    minutes) is REALLY bad during a demo.  I created an isolated LAN, just
    a DEChub900 and 90 with a PC to demo and assure that there was no other
    bad network juju on the wires...
    
    So....anything that u can do re:Performance is badly needed...
    
    Thanks!
    j
1453.3HUBWATCH_GO_FASTNETCAD::DRAGONTue Sep 20 1994 12:517
    
    Gee Tom,
    
    	Don't you think its time to tell the field about that logical that
        makes it go faster:-)
    
    Bob
1453.4Fresh brewed Xircomian CoffeeANGLIN::BERNDTWed Sep 21 1994 22:3212
    I am sitting here sipping my Espresso after a fun day of Novell/Digital
    presentations in the windy city. Tom's response in .1 gave me my first
    good laugh today...nice that every one has a sense of humor.
    
    I do agree with John, it X313 seems considerably slower than customer
    v2. But, considering the added functionality-maybe it's somewhat
    "excusable". BTW I am running on a 320P with 8mB ram and Xircom. You
    know the Xircom smelled a bit like fresh brewed coffee when doing some
    commands...hmmmmm???
    
    Ron