Alanxtl commented on code in PR #3502: URL: https://github.com/apache/dubbo-go/pull/3502#discussion_r3658422561
########## integrate_test.sh: ########## @@ -20,7 +20,7 @@ set -e echo "start integrate-test: repo = $1, SHA = $2, branch = $3" -# set root workspace +# set root workspace (already checked out dubbo-go code) Review Comment: do not summit these useless editing ########## README.md: ########## @@ -146,6 +146,32 @@ A warning-only scanner that detects exported variadic RPC contracts and prints m Run `make rpc-contract-check` to use it locally. +### [benchmark](https://github.com/apache/dubbo-go/tree/main/tools/benchmark) + +A performance benchmark suite for comparing **Dubbo-Go**, **Dubbo-Java**, and **gRPC** frameworks across multiple dimensions including throughput (QPS), latency (p50/p90/p95/p99), and resource usage (CPU, memory). + +**Key Features:** +- Multi-dimensional testing: payload size, serialization, compression, concurrency, and call modes +- Frameworks: Dubbo-Go (Triple), Dubbo-Java, and gRPC +- Output: JSON reports with QPS, latency percentiles, and system resource metrics +- Automation: scripts for code generation and batch execution + +**Quick Start:** + +```bash +# Start a Dubbo-Go server +cd tools/benchmark/server/dubbo-go && go run main.go --port 20000 + +# Run a single benchmark +cd tools/benchmark && go run client/main.go \ + --framework dubbo-go --payload 1024 --concurrency 100 --mode unary + +# Run all benchmarks +./tools/benchmark/scripts/run_all.sh +``` + +For usage details, see the [benchmark README](./tools/benchmark/README.md). Review Comment: reference other tools, do not take up so much README space -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
