[GitHub] [apisix] fankeke commented on issue #2188: request help: url_block.lua plugin: Is there any performance bottleneck if there are many block rules, say 1000000 url rules in production envirome

2020-09-15 Thread GitBox
fankeke commented on issue #2188: URL: https://github.com/apache/apisix/issues/2188#issuecomment-692671931 Can we divide the 1+ million block urls into groups according to their hosts? === @spacewander the whole 1+million urls only for one host(upstream) :) -

[GitHub] [apisix] fankeke commented on issue #2188: request help: url_block.lua plugin: Is there any performance bottleneck if there are many block rules, say 1000000 url rules in production envirome

2020-09-12 Thread GitBox
fankeke commented on issue #2188: URL: https://github.com/apache/apisix/issues/2188#issuecomment-690832270 Improving performance mainly depends on the quality of the rules. === thanks for reply In our system, there are already 1+ million block urls, if every request sho

[GitHub] [apisix] fankeke commented on issue #2188: request help: url_block.lua plugin: Is there any performance bottleneck if there are many block rules, say 1000000 url rules in production envirome

2020-09-10 Thread GitBox
fankeke commented on issue #2188: URL: https://github.com/apache/apisix/issues/2188#issuecomment-690832270 Improving performance mainly depends on the quality of the rules. === thanks for reply In our system, there are already 1+ million block urls, if every request sho

[GitHub] [apisix] fankeke commented on issue #2188: request help:

2020-09-08 Thread GitBox
fankeke commented on issue #2188: URL: https://github.com/apache/apisix/issues/2188#issuecomment-689251844 Every request will be handled by block plugin. This is an automated message from the Apache Git Service. To respond

[GitHub] [apisix] fankeke commented on issue #2188: request help:

2020-09-08 Thread GitBox
fankeke commented on issue #2188: URL: https://github.com/apache/apisix/issues/2188#issuecomment-689251456 @membphis This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHu