Ethereal-dev: Re: [Ethereal-dev] Ethereal performance, after Guy's changes ...

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: "Lars Ruoff" <lars.ruoff@xxxxxxxxxxxxxxxxxx>
Date: Wed, 19 Nov 2003 11:09:56 +0100

> The RTP thing should ONLY register the tap if the user has requested it.
>
> If that requires a complete redissection of the entire file, so be it.
> All other taps require a full redissection of the entire file anyway.
>
> Users not wanting/using RTP analysis should not be disadvantaged by having
> the RTP thing
> comsuming both memory and CPU.

I fully agree with this.
(However CPU consumption is negligible and memory consumption is
proportional to number of RTP streams in the capture - no memory consumed if
no RTP packets in the capture).
But a user preferences option for that would be fine.

Note that there are 2 taps:
RTP Streams and RTP Analysis.
RTP Streams just collects information about streams and is quite fast (this
is the one registered on startup).
RTP Analysis does the heavy analysis and is registered temporarily while
analysing only (and i'm currently finishing work on a "fast analysis"
architecture where this will be made without registering a tap at all)

Lars Ruoff