benchmarks: add and fix some benchmarks#7989
Conversation
There was a problem hiding this comment.
These are great and very much appreciated changes...you've made several recently. Thanks a ton!
If you aren't aware, these run continuously on pipelines on the master branch: https://buildkite.com/gvisor/pipeline/builds?branch=master
The results automatically post profiles to the BuildKite run. Use them if you find them useful.
Additionally, we have an internal dashboard where the results are posted and we find regressions pretty well with that dashboard. We haven't released it because 1) some internal process and 2) they run on ptrace and KVM platforms on GCP machines. Ptrace is a stable platform but with bad performance and KVM uses nested virtualization in GCP (we reccomend baremetal KVM for production services).
How useful would this dashboard be to you?
Awesome! Now the official performance report of gvisor , which is visible from outside, is https://gvisor.dev/docs/architecture_guide/performance/. So I think it will be great to have a dashboard to post the performance metrics of all benchmarks from different versions, which helps the regressions and also helps the comparison of different platforms. |
f133297 to
0ed1876
Compare
It will take me some time to do this, but I'll see if I can get it done. I think your contributions deserve some investment here. Thanks again. |
Signed-off-by: Chen Hui <cedriccchen@tencent.com>
0ed1876 to
559e457
Compare
Signed-off-by: Chen Hui <cedriccchen@tencent.com>
Signed-off-by: Chen Hui <cedriccchen@tencent.com>
According to MakeCmd function of fio, the unit of --size option is MB. Signed-off-by: Chen Hui <cedriccchen@tencent.com>
Signed-off-by: Chen Hui <cedriccchen@tencent.com>
According to iperf help page: ``` -l, --len #[kmKM] length of buffer in bytes to read or write (Defaults: TCP=128K, v4 UDP=1470, v6 UDP=1450). ``` So "--length 64K" option is invalid for iperf, actually it will be regard as default option "--len 128K". Signed-off-by: Chen Hui <cedriccchen@tencent.com>
Signed-off-by: Chen Hui <cedriccchen@tencent.com>
559e457 to
bef569a
Compare
|
Hi @zkoopmans , is there any other suggestion? |
|
Nope, you're good. I'll make sure this gets merged. |
Also, revise hackbench to use b.N to scale. There was some discussion on the [original PR](#7989 (comment)) about making this fixed. However, after looking again, loops should scale by b.N. Fixed number of loops can use -test.benchtime=100x or whatever and comparison can be done using golang's 'ns/op' metric where the op is number of loops. PiperOrigin-RevId: 487678691
benchmarks: add and fix some benchmarks