Not sure what to make of this. I'm seeing it every few hours.
Hi Count,
We have seen large environments run without this issue and smaller ones have the issue so it's not scale alone causing it. Some of the issue may be coming from the NTA deployment and overall environment. BTW SP2 is in support and will GA soon. It continues to improve performance.
Andy
Hi Jeff,
It's one of the mechanisms SP1 uses to keep the server from overloading.
Hi Andy. I'm a bit concerned here in that this SP1 mechanism is in place to stop the queue overloading and consuming memory. Am I to take from this that the product will only scale to a certain amount of flows before the database writes can no longer keep up with the incoming flows? If so, what is the amount of flows that could be expected to work before problems such as this expect to happen? It seems that potentially, this product wont scale to too many interfaces / flows. Are you able to clarify this please?
Thanks
Thanks Andy. I'm actuallly running an evaluation of this at present and look like we'll buy the entire product suite within the next few weeks. Whilst I've been able to determine features and functionality in an isolated test, I haven't been able to ramp up to a full scale implementation and hence my concern about scalability. We would be looking to run upwards of 250 interfaces for netflow along and I'd appreciate it if you could confirm with you where this sits in your definition of "small / large environment" ! Also, are you able to offer any indication as to how i could calculate the size requirements for this netflow feature? There must be some guidelines ?
Thanks again.
Cheers
