You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@EtiennePerot
I'm working on the issue now, I found that the main reason might be related with runsc package.
If we run the command $ make benchmark-platforms BENCHMARKS_TARGETS=test/benchmarks/base:syscallbench_test, we'll get numerous profiling files under /tmp/profile . However, the files under /tmp/profile/runsc/ are missing as you mentioned in the issue.
Those profiling files for the runtime runsc should be created via
. I follow the steps from make dev then sudo make run-benchmark BENCHMARKS_TARGETS=test/benchmarks/base:syscallbench_test RUNTIME=runsc , I found the Start() function under runsc profile package is never called.
I want to ask in what step should the runsc profile Start() function be called ?
If it's called properly then the files should be created ,too.
Description
Running a benchmark like:
(which uses the default value for
BENCHMARKS_PROFILE
which is-pprof-dir=/tmp/profile -pprof-cpu -pprof-heap -pprof-block -pprof-mutex
)... results in warnings about the profiling not working:
... and no profiles stored under
/tmp/profile
.Steps to reproduce
runsc version
docker version (if using docker)
uname
6.6.15
kubectl (if using Kubernetes)
repo state (if built from source)
head
runsc debug logs (if available)
No response
The text was updated successfully, but these errors were encountered: