Message-ID: <3DB5A4A3.6602EE45@hp.com> Date: Tue, 22 Oct 2002 12:18:59 -0700 From: Rick Jones <rick_jones2@hp.com> Subject: Re: tcptrace and huge files ? (a few GB)
> tcptrace have memory problems when procesing large files. I think the
> best solution is to prefilter the trace with tcpdump.
It can also have file descriptor limit problems when generating the
xplot files... I've run into that - not sure if I was trying to run a
64-bit compiled tcptrace at the time or not.
I figure that the only "complete" soltuion other than a 64-bit
application with no file descriptor limits would be some sort of
heuristic where tcptrace decides to "swap-out" a connection to a temp
file (think backing store) or something when it has gone say N packets
past the FIN or RST in the trace. that, or once it has state for M flows
already running.
it would still need/want to keep an N-tuple/flow to backing store
mapping (think TLB/pdir) in memory
i suspect it would be straight-forward, but non-trivial, but I've never
actually writen anything like that so I could be completely wrong.
rick jones
-- Wisdom Teeth are impacted, people are affected by the effects of events. these opinions are mine, all mine; HP might not want them anyway... :) feel free to post, OR email to raj in cup.hp.com but NOT BOTH... ---------------------------------------------------------------------------- To unsubscribe, send a message with body containing "unsubscribe tcptrace" to majordomo@tcptrace.org.
This archive was generated by hypermail 2b30 : 10/23/02 EDT