Wireshark-dev: Re: [Wireshark-dev] slow startup caused by splash_update?
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Jeff Morriss <jeff.morriss.ws@xxxxxxxxx>
Date: Mon, 06 Apr 2009 13:53:30 -0400


Jeremy Linton wrote:

Jeff Morriss wrote:

Once Wireshark is up, is it usable [going to Gerald's suggestion]?
Its a little lagy but usable. I wouldn't want to use it all day long, but its ok for intermittent use. My feeling is that its slower than other things running on that machine over X (yast, xterm, emacs, etc). Those are all pretty usable.
How about some other GTK2 application? My recollection is that GTK2 is pretty talkative (in terms of X traffic). 


In those applications the lag is there, but its not bothersome at all. The ping latencies are fairly fast

  icmp_seq=1 ttl=64 time=2.59 ms
  icmp_seq=2 ttl=64 time=0.409 ms
  icmp_seq=3 ttl=64 time=0.702 ms
  icmp_seq=4 ttl=64 time=0.623 ms
  icmp_seq=5 ttl=64 time=0.967 ms


Really what was killing me was the startup time.


Weird.  I don't know what to make of that.