You load it into kcachegrind. I found a compiled windows version on sourceforge (I think http://sourceforge.net/projects/precompiledbin/). Martin
On Thu, Sep 12, 2013 at 1:54 PM, Anders Broman <anders.bro...@ericsson.com>wrote: > > > -----Original Message----- > From: wireshark-dev-boun...@wireshark.org [mailto: > wireshark-dev-boun...@wireshark.org] On Behalf Of Evan Huus > Sent: den 12 september 2013 13:15 > To: bal...@balintreczey.hu; Developer support list for Wireshark > Subject: Re: [Wireshark-dev] Performance degradation in trunk > > On 2013-09-12, at 5:40 AM, Bálint Réczey <bal...@balintreczey.hu> wrote: > > >> Could they analyze perf results or run git bisect to find the point > >> when the degradation started? > > >Since this is on Ubuntu (which can run valgrind) just use the -p option > to tools/valgrind-wireshark.sh and it will produce a performance profile. > Do that for >both builds and we'll have something to work with. > > > >Evan > > Here's the output from "trunk", how do you get anything useful from it? > /Anders > > >PS I suspect some new heuristic dissector has been introduced, since none > of the other changes from 1.8 to trunk are likely to have such a > significant >performance impact. > > > Cheers, > > Balint > > > > 2013/9/12 Anders Broman <anders.bro...@ericsson.com>: > >> Hi, > >> > >> I recently supplied some people with an internal build from recent > >> trunk and got complaints on performance. Switching back > >> > >> To the default Wireshark on the Ubuntu 13.04 system 1.8.2 reading of > >> a 400M trace file with SIP Diameter etc traffic is more than twice as > fast. > >> > >> Regards > >> > >> Anders > > > ___________________________________________________________________________ > > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > > Archives: http://www.wireshark.org/lists/wireshark-dev > > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > > > > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe >
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
