archine opened a new issue, #11493: URL: https://github.com/apache/apisix/issues/11493
### Description I run apisix through docker-compose on two different servers, and the memory footprint gap is too large. The configuration file and the image version are the same. ### 效果图 * server-1  * server-2  ### 配置文件 * docker-compose ```dockerfile version: '3.9' services: etcd: image: bitnami/etcd:3.5.14 container_name: etcd restart: always environment: ALLOW_NONE_AUTHENTICATION: "yes" ETCD_ENABLE_V2: "true" ports: - "2379:2379" - "2380:2380" networks: - apisix volumes: - /home/etcd:/bitnami/etcd - ./conf/etcd.yml:/opt/bitnami/etcd/conf/etcd.yaml deploy: resources: limits: cpus: '2' memory: 2048M reservations: cpus: '1' memory: 512M apisix: image: apache/apisix:3.9.1-debian container_name: apisix restart: always ports: - "9080:9080" - "9443:9443" - "9180:9180" - "9090" networks: - apisix volumes: - ./conf/apisix.yml:/usr/local/apisix/conf/config.yaml depends_on: - etcd deploy: resources: limits: cpus: '2' memory: 2048M reservations: cpus: '1' memory: 1024M networks: apisix: driver: bridge ``` * apisix configuration file ```conf apisix: node_listen: 9080 ssl: enable: true listen: - port: 9443 enable_control: true control: ip: "0.0.0.0" port: 9090 deployment: admin: allow_admin: - 0.0.0.0/0 admin_key: - name: "admin" key: "xxxxxxxxxxxxx" role: admin etcd: host: - "http://etcd:2379"; prefix: "/apisix" timeout: 5 nginx_config: http: client_body_timeout: 180s client_max_body_size: 100m send_timeout: 60s plugins: - jwt-auth - key-auth - cors - ip-restriction - limit-count - limit-req - limit-conn - proxy-rewrite - response-rewrite - redirect - request-id - gzip - real-ip - client-control - api-breaker - traffic-split ``` ### Environment * APISIX: 3.9.1 * System: 5.4.0-190-generic * nginx version: openresty/1.25.3.1 * etcd: 3.5.14 -- 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]
