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: Andrew Hood <ajhood@xxxxxxxxx>
Date: Tue, 07 Apr 2009 20:03:44 +1000
Nathan Jennings wrote:
> On 4/6/2009 11:24 AM, 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. 
>>In those applications the lag is there, but its not bothersome at all. The ping latencies are fairly fast
> 
> 
> This may not apply to you, but in my experience we've had slow rendering 
> times due to our Microsoft Windows X servers not supporting anti-aliased 
> font rendering. We worked around this in the past by disabling 
> anti-aliased fonts in GTK.

Slow startup doesn't only apply to GTK. Motif apps are also noticably
slow to start over my ADSL2+ link. Snooping that traffic shows huge
amounts of chatter as the client queries the server for the fonts it
supports. LBX speeds things up (sometimes dramatically), but not all X
servers support it. Reducing the fonts the X servers supports speeds
things up too.

-- 
There's no point in being grown up if you can't be childish sometimes.
                -- Dr. Who