Description of problem:
On running a benchmark tests to create 2k app pods(nginx) and routes on GCP openshift environment with OVNKubernetes CNO, the cluster routes like console, prometheus goes nonresponsive for few minutes and its takes longer(at least 13min) to access the new app routes and hence the test fails consistently. Observed this behavior frequently and spike in ovnkube-master CPU utilization to 6 cores as well. 

Version-Release number of selected component (if applicable):
OCP 4.10.5 GA

How reproducible:
Always on GCP

Steps to Reproduce:
1. Deploy a healthy cluster with atleast 24 worker nodes(8 cpu, 32G mem) on GCP using OVNKubernetes CNO
2. Run kube-burner workload to create 2k pods and routes across multiple namespace 
3. Watch the console or prometheus routes times out during the workload as well as any new application routes takes longer to be reachable
4. ovnkube-master cpu utilization increases to 6 cores

Actual results:
The dataplane test fails during connectivity check because the routes are unreachable after kube-burner finishes creating them. Turns out NBDB is still having load_balancers being added about 13 mins after the services were created. addlogicalports for pods are also exceeding 1s

Expected results:
it should be available within SLA and this workload should not affect other cluster routes 

Additional info: