shuaijinchao commented on issue #73: URL: https://github.com/apache/apisix-go-plugin-runner/issues/73#issuecomment-1073901699
hi, @Horus-K I used did comparison test with your configuration, and the average processing time of GoRunner and APISIX native plugins in the same scenario is nearly 3 times different, QPS GoRunner is about 30% lower. The current consumption may mainly come from data replication between processes and parsing of protocol data in Runner. ### html response ```bash # GoRunner $ wrk -t 8 -c 200 -d 10s http://192.168.56.199:9080/hello Running 10s test @ http://192.168.56.199:9080/hello 8 threads and 200 connections Thread Stats Avg Stdev Max +/- Stdev Latency 96.26ms 215.11ms 1.94s 93.97% Req/Sec 533.43 230.84 2.01k 73.43% 42405 requests in 10.03s, 64.99MB read Requests/sec: 4228.93 Transfer/sec: 6.48MB # APISIX $ wrk -t 8 -c 200 -d 10s http://192.168.56.199:9080/world Running 10s test @ http://192.168.56.199:9080/world 8 threads and 200 connections Thread Stats Avg Stdev Max +/- Stdev Latency 39.52ms 50.57ms 830.05ms 96.40% Req/Sec 767.96 104.59 1.42k 88.25% 61186 requests in 10.01s, 93.77MB read Requests/sec: 6112.90 Transfer/sec: 9.37MB ``` ### say hello response ```bash $ wrk -t 8 -c 200 -d 10s http://192.168.56.199:9080/hello Running 10s test @ http://192.168.56.199:9080/hello 8 threads and 200 connections Thread Stats Avg Stdev Max +/- Stdev Latency 1.71s 1.61s 6.91s 48.98% Req/Sec nan nan 0.00 0.00% 52485 requests in 10.01s, 10.46MB read Requests/sec: 5244.93 Transfer/sec: 1.05MB $ wrk -t 8 -c 200 -d 10s http://192.168.56.199:9080/world Running 10s test @ http://192.168.56.199:9080/world 8 threads and 200 connections Thread Stats Avg Stdev Max +/- Stdev Latency 524.45ms 563.29ms 2.39s 81.96% Req/Sec nan nan 0.00 0.00% 75067 requests in 10.00s, 13.31MB read Requests/sec: 7505.93 Transfer/sec: 1.33MB ``` -- 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]
