Slow response as many routes exist

[shadow3x3x3]

All config of apisix is default.

There are 20,000 routes in apisix. We added a new route and found that responding to the new route takes about 1.8 seconds for an HTTP response. Is this normal?

Thank you.

[tzssangglass]

Not normal, we can add the prometheus plugin to see where the delay is?

[shadow3x3x3]

@tzssangglass Yes, that's the original log, but that's okay. I think the error was caused by heavy loading during testing.

We want to use APISIX for our multiple services. If APISIX can hold 200,000 routes, it might be a better choice than other api gateways for us.

[tokers]

@shadow3x3x3 So you're testing the extreme case?

[shadow3x3x3]

@tokers Yes.

[tzssangglass]

Yes, that's the original log, but that's okay. I think the error was caused by heavy loading during testing.

I think the 502 issue is caused by bad upstream format and address(http:/1.1.1.1:80/) than heavy loading ,you could change the upstream to a normally accessible address to rule out if the 502 issue is arising from this.

[moonming]

@shadow3x3x3 This is an interesting scenario, we can talk in more detail, I am the PMC chair of Apache APISIX.
You can reach me at wenming@apache.org or https://calendly.com/wenming/30min