Ethereal-dev: Re: [Ethereal-dev] Performance. Ethereal is slow when using largecaptures.

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: "Ronnie Sahlberg" <ronnie_sahlberg@xxxxxxxxxxxxxx>
Date: Sun, 16 Nov 2003 14:24:13 +1100
----- Original Message ----- 
From: "Guy Harris"
Sent: Sunday, November 16, 2003 11:04 AM
Subject: Re: [Ethereal-dev] Performance. Ethereal is slow when using
largecaptures.


> Note also that it will probably consume a significant amount of memory -
> in fact, it already *does* consume a significant amount of memory,
> because the GtkClist for the summary pane keeps strings for all the
> values.

As long as there is an option to control whether the current-memory-saving
method is used or the new
filter-faster-but-eat-enormous-amounts-of-memory mode is available, and that
that option defaults
to use the current method.

I can enable this feature IF I want to then and if I am aware that it wille
at memory like there is no tomorrow.

That is fine because for very large captures:
I can buy a magnitude more memory than I currently have.
However, I can not buy a CPU that is even just twice as fast as the one I
have today.