Two questions.
1). If the CSS marks a flow for clean-up due to matching the idle timeout value, and then the flow becomes active again before it is reclaimed...what happens? Is the flow still subject to cleanup if the threshold is met (25% of available resources or something like that)?
2). The CSS grabs a bunch of memory at startup for FCB's..what about permanent flows (flow timeout multiplier set to 0)? I have a customer who wants at least 80 idle flows to not timeout, ever. I'm concerned that the amount of resources consumed or dedicated will be damaging - but the question is how much resources would 80 connections actually utilize? I realize that TCP flow uses two FCBs...so what does that equal in memory/processor/etc.?
