> (performace simply sucks, if a 100MB trace file is loaded). ...which needs to be fixed (some profiling results suggest that the heavy use of "printf"-family routines when generating the lines in the packet list display contributes significantly to this; making "ip_to_str()" and "ether_to_str()" generate the strings by hand helped a bit, but not a lot - and the "printf"-family routines and stuff they call still contributed a lot; Microsoft Network Monitor read in one large trace file significantly faster than did Ethereal), but, at least as a short-term workaround, it sounds as if a file-reading filter would be useful.
Powered by MHonArc 2.6.10