xiaokunliu opened a new issue #6660:
URL: https://github.com/apache/apisix/issues/6660


   ### Description
   
   now then i have a question as follow:
   i use opneresty and apisix deployed on k8s, on request uri 
   apisix/hello : client -> nlb -> apisix -> nginx
   nginx/hello: client -> nlb ->  openresty -> nginx
   
   pod config is the same: 4c8g for apisix and openresty
   
   apisix and openresty use config is the same as follow:
   use epoll;
   worker_processes 4;
   worker_connections  32768;
   
   upstream config is the same as follow:
   openresty config:
   upstream nginx_backend {
           server nginx.test1.svc.cluster.local:80;
           keepalive 320; 
           keepalive_timeout  500s;
           keepalive_requests 1000000;
       }
   
   apisix have config it at the dasborad upstream config as the same with 
openresty upstream config as follow:
   <img width="1124" alt="image" 
src="https://user-images.githubusercontent.com/12118125/158988478-4d25c3a4-4400-4800-aeb0-a44b4e472b1e.png";>
   
   
   now i have a benmarch report, the apisix throught is less than openresty
   
   
   apisix benmarch report:
   <img width="1076" alt="image" 
src="https://user-images.githubusercontent.com/12118125/158986212-96157bb6-480a-4697-98f5-060c1d8468e9.png";>
   
   
   nginx benmarch report:
   <img width="1339" alt="image" 
src="https://user-images.githubusercontent.com/12118125/158986357-3d83ae22-7bb4-4e77-8b4f-28b874f24d73.png";>
   
   
   
   ### Environment
   
   - APISIX version (run `apisix version`):
   - Operating system (run `uname -a`):
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to