I think there is only a practical limit in the number of nodes in a pool - for example, if you have a large number of nodes, all the traffic for all of those nodes will be routed through the Traffic Manager (or cluster of Traffic Managers). Can you share more information about the design which you are considering?
Regards, PaulW, ...
Hi, we currently have a cluster of 4 traffic managers and a pool with 6 nodes being serviced in it. Someone from the architect team came and asked me what the maximum number of nodes in a pool could be on our devices. I am not part of the design team just trying to get the information he asked for. We do have this running on one interface so ingress and egress traffic is on the same interface so that may also affect performance. I was just wondering if maybe there is something where you can put in the details of the traffic managers build and nodes that could work out a maximum or until the service degrades. Not even sure if I am asking the right questions.
Probably best to discuss with your technical contact here, as a lot will depend on your architecture, and this sounds like a large implementation. But the practical limit will be set by the throughput of the systems hosting the traffic managers, and the overall licensed bandwidth. You can also use the graphic analysis to gather data for capacity planning and to test for when the service degrades.
If you are planning to use autoscaling, you can set the maximum number of nodes in the configuration, and Traffic Manager will monitor the SLA to spin new nodes up and down to meet the thresholds.