Ethereal-dev: Re: [Ethereal-dev] Reassembling out of order packets

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Guy Harris <gharris@xxxxxxxxx>
Date: Thu, 28 Oct 2004 22:58:01 -0700
Jerry Talkington wrote:

On Thu, Oct 28, 2004 at 12:40:52PM -0700, Guy Harris wrote:



   2) the text widget that displays the raw packet data being slow
dealing with very large amounts of text (which it *definitely* is)



Yes, that does have some impact, but I'm usually on machines with gobs
of RAM (1 to 2 gigs, which at least used to be gobs.)
I'm not talking about slowness due to paging, I'm talking about CPU-speed slowness. When dealing with a reassembled packet (NIS YP_ALL response) with 437188 bytes in it (no, that's not a typo), it's *really* slow when building the packet data display (and also ... 


   3) the code to build protocol trees, or the tree widget, being slow in
dealing with very large protocol trees (the code to build protocol
trees should be O(n) in the number of nodes, but the tree widget might
be O(n^2) if, for example, it appends to lists by starting at the
beginning of the list and scanning to find the end)?


...apparently really slow when building the packet details display.
No paging, according to Activity Monitor on my 1GB PowerBook. 100% CPU, though (97% user mode).