https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16281
Jim Young <jyo...@gsu.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jyo...@gsu.edu
--- Comment #15 from Jim Young <jyo...@gsu.edu> ---
Hello Tomasz,
I believe your fix has made a huge difference in usability of the tcptrace
graph.
I did a pair of tests using dev installers generated by the macOS buildbots.
3.3.0rc0-772-gd87bce7c4fc3 <=== Last installer prior to your patch.
3.3.0rc0-776-g5cb8343fb9d1 <=== Installer several commits after your patch.
Starting with a capture with a single TCP stream of 467525 packets with a
duration of 3.75 seconds.
Using buildbot version "3.3.0rc0-772-gd87bce7c4fc3", the last version prior to
your patch, the capture file took 12 seconds to initially load, 16 seconds to
initially open the tcptrace graph and whopping 10 minutes and 53 seconds to
zoom into a small section of packets at the 1 second mark.
Using buildbot version 3.3.0rc0-776-g5cb8343fb9d1, a version with your patch
included, the capture file took 12 seconds to initially load, 16 seconds to
initially open the tcptrace graph and when zooming into a small section of
packets at the 1 second mark the graph response was virtually instantaneous.
The tcptrace graph now appears to be the quickest of the five grpah types to
display and reset. If I choose any of the other graph types there is about an
8 second delay before the new graph is displayed. All graph types feel
responsive to zoom actions. Clicking [Reset] on any but the tcptrace graphs
incurs about a 8 second delay.
One observation I had regrading the behavior before your patch. I believe I
only saw the "hang" on the initial attempt to zoom into the tcptrace graph.
Once zoomed in I could do other zoom actions (in or out) and scroll around the
tcptrace graph with no delays. If I viewed one of the other TCP graphs and
then came back to the tcptrace graph I would have to wait the approximately 11
minutes for the initial zoom to complete.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
