09-12-2002 03:52 AM
I'd like to know if anyone can give a good definition of the Arrowpoint Caching Algorithm (ACA) used on the CSS 11000 series of content switches. There's a definition in the manual, but it's pretty basic; stating that it bases it's handling based on load and availability. I'd like to know if there are definite parameters that control this, if they're configurable, or if the algorithm itself is a corporate secret.
Thanks for any information!
09-19-2002 07:33 AM
Of course it will be confidential as the name indicates.
10-07-2002 08:25 PM
As to the INs and OUTs of the algorithm .... good luck ... on the other hand the following link might help answer some of your questions:
http://www.cisco.com/warp/public/117/configuring_aca.html
*As you can see there are a couple of parameters that you can manipulate.
Cheers,
Leonel
10-16-2002 08:46 AM
Hi, Balance ACA will require a minimum of 300 flows per second to set up correctly and then need to average 1000 flows per second to evenly distribute load. Using this algorythm will require a consistant flow level.
ACA is optimized it for the average case performance
where the behavior is better as more flows are passed through the box.
For small numbers of flows, you might experience what appears to be
"erratic" behavior. You will see below that it is a compromise between
getting the best behavior in the long run and yet maintaining stability
and minimal sampling impact.
Hope this helped!
Jim
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide