Wireshark-bugs: [Wireshark-bugs] [Bug 7527] Repeated filter operations are unnecessarily slow
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7527
Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeff.morriss.ws@xxxxxxxxx
--- Comment #2 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2012-07-25 14:02:23 PDT ---
(In reply to comment #0)
> 1) Cache the packet list for the last N filters that have been applied to an
> open capture file.
>
> This should make a massive improvement to the execution time of filters in long
> sessions. Bonus points for a UI indication of which filters in the filter
> history have been cached (could highlight the history entry in light green, for
> example). More bonus points for making N configurable (I suspect that changing
> N should also change the number of filters that are kept in the filter history
> as well).
We (or at least Gerald and I) discussed this at Sharkfest '12. When we were
first discussing it the thought was that all one needed was to store whether
each frame passed the dfilter or not. But it's more complex: we'd need to be
able to reconstruct everything in the frame_data. Fortunately a lot of that
comes from the file (meaning we could avoid saving a copy of the entire
frame_data array at the expense of having to re-read the file). It should be
noted that the frame_data is one of the largest users of memory in Wireshark.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
