Wireshark-dev: [Wireshark-dev] Qt Interface Profiling
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Evan Huus <eapache@xxxxxxxxx>
Date: Fri, 26 Jun 2015 14:45:22 -0700
I just ran the Qt interface through callgrind while loading a fairly
large capture. Stripping out all the dissector-related expenses, the
following two UI functions show up as hot spots:

qt_blurImage()
This is a Qt internal function for blurring, presumably from the fancy
start-up screen, but showed up as *surprisingly* expensive given the
fact that the startup screen was only a tiny fraction of the time
profiled. Is it possible it's still getting run with a blur factor of
0 on every screen or something?

PacketListModel::recordLessThan()
This is ours, used for sorting the packet list. Not immediately sure
how to make it better, the GTK version is entirely different.

Cheers,
Evan