From: Manikantan Ramadas (mramadas@masaka.cs.ohiou.edu)
Date: 11/04/04
Date: Thu, 4 Nov 2004 18:31:02 -0500 From: Manikantan Ramadas <mramadas@masaka.cs.ohiou.edu> Subject: Re: tcptrace taking a very very long time Message-ID: <20041104233102.GB20956@masaka.cs.ohiou.edu>
[Apologies to every one receiving multiple copies of this mail. Had to
reply to tcptrace@tcptrace.org where this query was received from, to
close the thread.]
A bug found in the AVL Tree search compare function has been fixed
now. It should be available as release 6.6.7 from the tcptrace website
downloads page. This would probably take care of the problems reported
in this thread.
Thanks,
Mani.
On Mon, Nov 01, 2004 at 09:04:39AM -0500, Russ Fink wrote:
> Sad to say (and I'm sure I will get flames), tcptrace is broken in this
> regard. It does not work for very large cap files.
>
> What you are experiencing is an endless loop in the AVL tree data structure
> with regard to the rotates. I have experienced this same problem a couple
> months back (whatever the current version was) and manually rolled out the
> AVL tree and reverted to the hash table. [I don't currently use tcptrace
> because I needed additional features and switched to an internal tool.]
>
> To the community, hash tables are the most efficient way to manage
> connections in any kind of TCP system. Any kind of tree structure or
> queue, which tries to do constant optimization of its internal structure,
> is doing way more work than necessary. Look at libnids
> (libnids.sourceforge.net) and see how that is implemented using hashes.
>
> Russ
>
>
> ----------------------------------------------------------------------------
> To unsubscribe, send a message with body containing "unsubscribe tcptrace"
> to
> majordomo@tcptrace.org.
-- "'Beauty is truth, truth beauty,'--that is all Ye know on earth, and all ye need to know." - John Keats ____________________________________________________________________ * Manikantan Ramadas * IRG, OU * http://irg.cs.ohiou.edu/~mramadas * ____________________________________________________________________
----------------------------------------------------------------------------
To unsubscribe, send a message with body containing "unsubscribe tcptrace" to
majordomo@tcptrace.org.
This archive was generated by hypermail 2.1.7 : 11/05/04 EST