I have 5 extcaps, and the difference is about half a second. Would be interesting, what kind of devices you have in your extcap list.
But in general, I still think the main time is loading the rest of interfaces, extcap is a very small part, just pushed the whole time over the top. cheers On Tue, Jan 9, 2018 at 2:38 PM, Anders Broman <anders.bro...@ericsson.com> wrote: > Hi, > Startup time with extcap: > 14:29:56.217 Main Info Wireshark is up and ready to go, elapsed time > 5485000 us > > Startup time with the new extcap parameter OFF > 14:30:40.559 Main Info Wireshark is up and ready to go, elapsed time > 3521000 us > > Still a lot of time is spent with the local interfaces > > 14:30:39.304 Main Info fill_in_local_interfaces() starts > : > 14:30:40.216 Main Info fill_in_local_interfaces() ends, taking 0.912s > 14:30:40.216 Dbg FIX: fetch recent color settings > 14:30:40.216 Capture Dbg sync_interface_stats_open > 14:30:40.216 Capture Dbg sync_pipe_open_command > 14:30:40.497 Capture Dbg read 6 indicator: S empty value > 14:30:40.559 Main Info Wireshark is up and ready to go, elapsed time > 3521000 > > Regards > Anders > > -----Original Message----- > From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On > Behalf Of Guy Harris > Sent: den 8 januari 2018 02:46 > To: Developer support list for Wireshark <wireshark-dev@wireshark.org> > Subject: Re: [Wireshark-dev] Compiling with or without extcap > > On Jan 7, 2018, at 3:19 PM, Roland Knall <rkn...@gmail.com> wrote: > > > We had this discussion a bung of times. I have nothing against having a > preference, but I am very much against making not-loading extcap the > default. New users should not face a hassle to enable a capture interface, > but existing users, who wish to improve the performance in any way, can > profit from an option doing exactly that. > > > > So +1 on making this option available > > +1 > > > big -1 on making it default to not-loading > > +1 on the -1 :-) > ____________________________________________________________ > _______________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject= > unsubscribe > ____________________________________________________________ > _______________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject= > unsubscribe >
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
