title: What's the latency of the ALB Listener priority evaluation
body: <p>The way I have my app set up is:</p>
  
  <p>1 Application LoadBalancer with 2 listeners HTTP and HTTPS.</p>
  
  <p>For both of those listeners, I have, for each, a <a href="http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-elasticloadbalancingv2-listenerrule.html" rel="nofollow noreferrer">Listener Rule</a> set up that points to a target group.</p>
  
  <p>Each target group is its own application and has its own domain, which I use as a <a href="http://docs.aws.amazon.com/elasticloadbalancing/latest/APIReference/API_RuleCondition.html" rel="nofollow noreferrer">Rule condition</a> in the Listener (host header) for forwarding.</p>
  
  <p>The question I have is, since Listener Rules must have a unique <a href="http://docs.aws.amazon.com/elasticloadbalancing/latest/application/listener-update-rules.html#update-rule-priority" rel="nofollow noreferrer">priority</a></p>
  
  <p>Would there be any noticable latency in server responses, given that I had 100 Listener Rules that pointed to different target group that have different domains?</p>
  
  <p>I'm worried about, say, the 100th Listener Rule causing slow performance for the Target Group it's forwarding traffic to</p>