Cool. Once again the ethereal team is scoring a complete and crushing
victory. Like as when the ozzies are playing a normal cricket one day
test.
Ill try it with one of my mother-of-all-packets.
Its a packet that once if has been reassembled in NBSS, SMB(Ttrans+Write)
and the DCERPC fragment layer becomes
>1MByte !!!!
I tell you, you do notice when ethereal hits the last fully reassembled
frame for that one and starts to dissect a >1 MByte PDU.
----- Original Message -----
From: "Guy Harris"
Sent: Thursday, December 04, 2003 10:08 PM
Subject: Re: [Ethereal-dev] ethereal performance
> On Wed, Dec 03, 2003 at 10:00:07PM +1100, Ronnie Sahlberg wrote:
> > Please keep ideas, patches and profile data coming.
>
> I've checked in a change to use our own data structure, rather than a
> tree of GNodes, for the protocol tree; it sped up one test case by
> 5-10%, and significantly sped up the processing of one capture with a
> large YPALL reply (as appending to the list of child nodes of a node is
> now constant-time rather than linear in the number of child nodes -
> "proto_node" structures have pointers to the first and last child).
> (Unfortunately, I suspect the GTree widget uses a tree of GNodes, so
> building the display for that packet is still slow.)
>
> Hopefully I haven't broken anything.
>
