Wireshark mailing list archives
Re: Performance degradation in trunk
From: Martin Mathieson <martin.r.mathieson () googlemail com>
Date: Thu, 12 Sep 2013 14:09:35 +0100
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.broman () ericsson com>wrote:
-----Original Message----- From: wireshark-dev-bounces () wireshark org [mailto: wireshark-dev-bounces () wireshark org] On Behalf Of Evan Huus Sent: den 12 september 2013 13:15 To: balint () 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 <balint () 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 optionto tools/valgrind-wireshark.sh and it will produce a performance profile. Do that for >both builds and we'll have something to work with.EvanHere's the output from "trunk", how do you get anything useful from it? /AndersPS I suspect some new heuristic dissector has been introduced, since noneof 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.broman () 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 asfast.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-request () 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-request () 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-request () 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-request () wireshark org?subject=unsubscribe
Current thread:
- Performance degradation in trunk Anders Broman (Sep 12)
- Re: Performance degradation in trunk Bálint Réczey (Sep 12)
- Re: Performance degradation in trunk Evan Huus (Sep 12)
- Re: Performance degradation in trunk Martin Mathieson (Sep 12)
- Re: Performance degradation in trunk Anders Broman (Sep 12)
- Re: Performance degradation in trunk Martin Mathieson (Sep 12)
- Re: Performance degradation in trunk Anders Broman (Sep 12)
- Re: Performance degradation in trunk Evan Huus (Sep 12)
- Re: Performance degradation in trunk Evan Huus (Sep 12)
- Re: Performance degradation in trunk Evan Huus (Sep 12)
- Re: Performance degradation in trunk Bálint Réczey (Sep 12)