Hi, There seems to be quite a performance hit with using the TreeView Widget: >From the bug reporter: >the trace file has only one stream (it's 6 minutes of HDTV), 440000 RTP-packets... (and the file is 50MBytes, this was the setting during >capture) The decoding is done for Ethernet/IP/UDP/RTP (no higher layer protocols) (since there is no signalling, I had to set the decoding to ' >RTP myself, " decode as"), the packets were truncated during capture to exactly 100 Bytes each. No filter is active. >I just redid the measurements and now have the numbers (not only the feeled time): >I selected a RTP-Packet, then "Analyse RTP-Stream" >Wireshark 1.0.6: 1 Minute >Developement version: 8 Minutes >The first refiltering is fast (15s on WS 1.06, 35s on Dev.version), the second one takes the rest... >A refresh seems to do the second refiltering... -> 7.5 Minutes on the Dev. Version.
Does some one know if it's possible to tweak the code to get better performance or is it best to back out the new code and retackle The old bug ? https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3246 I don't have a sufficently large RTP trace to test with at the moment. Regards Anders
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
