Match rules limit in virtualservce

Config
1
  1. is there a limit and performance impact if number of rules in virtualservice are high, for example, can i have 20k match rules in virtual service?
  2. instead of multiple exact matches, having a huge regex matching lets say 10k headers, which approach will be more performant?
  - match:
     - headers: 
        customer: 
            exact: "customer1"
    route:
      - destination:
          host: app1.frontend.svc.cluster.local
          subset: v1

the use case is, out of 20k total customers, 10k want to be on the v1 application version, can virtualservice scale to those many matching rules?