Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tracing perf regression on CI machine #78

Open
shuhaowu opened this issue Mar 20, 2024 · 2 comments
Open

tracing perf regression on CI machine #78

shuhaowu opened this issue Mar 20, 2024 · 2 comments

Comments

@shuhaowu
Copy link
Contributor

image

Now:

build/test/tests/cactus_rt_tracing_benchmark
2024-03-19T20:02:13-04:00
Running build/test/tests/cactus_rt_tracing_benchmark
Run on (12 X 4463.67 MHz CPU s)
CPU Caches:
  L1 Data 32 KiB (x6)
  L1 Instruction 32 KiB (x6)
  L2 Unified 512 KiB (x6)
  L3 Unified 16384 KiB (x1)
Load Average: 1.92, 0.44, 0.14
***WARNING*** CPU scaling is enabled, the benchmark real time measurements may be noisy and will incur extra overhead.
***WARNING*** Library was built as DEBUG. Timings may be affected.
---------------------------------------------------------------------------------------------------------
Benchmark                                                               Time             CPU   Iterations
---------------------------------------------------------------------------------------------------------
BM_ThreadTracerWithSpanEnabledNoCategory/iterations:10000000         2512 ns         2512 ns     10000000
BM_ThreadTracerWithSpanEnabledWithCategory/iterations:10000000       2529 ns         2529 ns     10000000
BM_ThreadTracerWithSpanDisabled/iterations:10000000                  18.6 ns         18.6 ns     10000000
BM_ThreadTracerWithSpanQueueFull/iterations:10000000                 2432 ns         2432 ns     10000000
@shuhaowu
Copy link
Contributor Author

Trying release build didn't help. It still complains about the same debug problem. Maybe something happened with the debian package.

@shuhaowu
Copy link
Contributor Author

Tried on the same machine with ubuntu docker container and the same problem, but no warning message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant