Wireshark-bugs: [Wireshark-bugs] [Bug 6755] slow loading/processing of conversations with over 5
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6755
--- Comment #7 from Cristian Constantin <const.crist@xxxxxxxxxxxxxx> 2012-01-27 00:46:35 PST ---
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > (In reply to comment #2)
> > > > (I haven't actually looked at the code ....)
> > >
> > > cristian: no one seems to be interested in this.
> >
> > On the contrary, I think there is interest but that no one has had the time to
> > review the changes yet. Please be patient.
>
> I ran a test with a trase of 220k packets and didn't notice any improvment att
> all, so your milage might vary.
> Regards
> Anders
cristian: this patch improves the behaviour (_orders of magnitude_)
when _one_ conversation has _lots_ of packets. I have tried to explain that
as clear as I could in the bug description. the problem itself lies in the
data structure and algorithm that are handling this case.
again, this appears in particular configurations: proxy/server to proxy/server
communication. for example sip proxies routing thousands of cps from one to
another.
my question is:
what does your trace contain?
a. lots of conversations, any conversation having a small number of packets?
(in this case, you are right there is no improvement)
b. small number of conversations, and at least one of them has a very large
number of packets (hundreds of thousands of packets)
(in this case, at least in all the tests that I have done the improvement in
terms of running time is of _orders of magnitude_. from tens of minutes to
tens of seconds)
bye now!
cristian
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
