Ethereal-dev: Re: [Ethereal-dev] Ethereal optimizations (proposals)

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 <guy@xxxxxxxxxxxx>
Date: Mon, 1 Dec 2003 14:14:12 -0800

On Dec 1, 2003, at 1:56 PM, Biot Olivier wrote:
I also suspect the conversation stuff is superlinear in time, explaining why 
captures with many conversations take ages to get read and parsed.
Some of it might be, although lookups are hashed, so they should be at worst linear in the number of conversations. 


| What is the "decoding dictionary"?  Do you mean the protocol
| trees for
| the packets?

I did not think at that initially; I first thought at packet start and
length information from the packet,
If by "packet start and length information" you mean the offset in the file of the packet data and the amount of packet data, that's already stored in memory in the frame_data structure. 


 but for the compressed files I meant the
intermediate states of the decompressor ("key frames") from where the
decompression can be resumed without knowledge of the prior data.


I have a not-complete attempt at saving that information in memory.