Wireshark-bugs: [Wireshark-bugs] [Bug 8460] IO Graph does not scale well with large captures
Comment # 6
on bug 8460
from Cristian Constantin
(In reply to comment #5)
cristian: hi. it works better now indeed. see some comments inline.
> (In reply to comment #4)
> > The limit of 100,000 entries is arbitrary but enforced because graphing at
> > that level is impossibly slow (the crash was because we weren't respecting
> > that limit in one place and running past the end of the array).
>
> This is still true.
cristian: what does it mean 100k packets nowadays when you have gigabits per
second in the core networks? anyway the real problem imo is that is not really
possible to select easily which are the 100k packets that should be shown.
>
> > I believe the slowness you're seeing is just that, it has to reprocess
> > 100,000 elements and draw them, which takes time. Presumably there's a
> > smarter or more efficient way to do this but I'm not at all familiar with
> > Cairo unfortunately.
>
> This is *not* true, I was wrong. It was a much subtler (but easier to fix)
> issue. It should be working fine (and relatively quickly, for that many
> elements) as of r48893.
>
> Cheers,
> Evan
You are receiving this mail because:
- You are watching all bug changes.
