[EMAIL PROTECTED] wrote on 02/28/2007 12:19:10 PM:
> I was troubleshooting an unrelated problem on our netflow cruncher this
> morning and discovered flow-capture chewing up RAM/Swap (to the point
> where it allocated all the swap on the box and was less-than-politely
> killed for doing so).
>
> This is the first time I've caught flow-capture being killed for using
> up too much RAM, but we've had to restart it on occasion for the same
> problem (flow-capture gets fat and makes our monitoring system cry about
> the flow-cruncher swapping too much).
>
> Two questions -
> 1) Is anyone else seeing this?
I'm seeing something similar. I happened to be doing a 'top' from the
command-line right after staring up several flow-captures. Was surprised
to see them start to take up 30-40% and higher CPU.
However, I noticed also that within 20 - 30 minutes each settled down to
their typical about 1%. The problematic flow-captures generally were those
with the least traffic.
Joe
_______________________________________________
Flow-tools mailing list
[EMAIL PROTECTED]
http://mailman.splintered.net/mailman/listinfo/flow-tools
