http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=289
------- Comment #4 from waters@xxxxxxxxxxxxxxx 2006-12-16 01:35 GMT -------
I just reproduced this bug with WireShark 0.99.4. Transport name resolution is
still slow on MacOS.
As I test, I timed loading an 8MB capture file.
Time to load capture file:
MacOS with transport name resolution enabled: 75 seconds
MacOS with transport name resolution disabled: 5 seconds
Linux with transport name resolution enabled: 12 seconds
Linux with transport name resolution disabled: 8 seconds
The file contains roughly 300 TCP and UDP conversations (as reported by tshark
-r <file> -q -z conv,{tcp,udp}), so loading it probably requires approximately
300 calls to getserv().
My back of the envelope math says that each unique transport name resolution on
MacOS costs roughly 0.23 seconds.
The Mac is a 1.33 GHz G4 running the MacPorts distribution of WireShark 0.99.4.
The Linux box is an AMD Sempron 2200+ running the Debian 0.99.4-3 distribution
of WireShark. Each had adequate free memory during the test.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.