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

[FR] Add support for adding custom profilers #1807

Open
xdje42 opened this issue Jun 28, 2024 · 0 comments
Open

[FR] Add support for adding custom profilers #1807

xdje42 opened this issue Jun 28, 2024 · 0 comments

Comments

@xdje42
Copy link
Contributor

xdje42 commented Jun 28, 2024

It is useful to get a trace of a benchmark, e.g., with DynamoRio (https://dynamorio.org/).

What's needed is a public API akin to the MemoryManager API that provides for wrapping the running of the benchmark.
Suitable binaries can register the profiler (akin to how a memory manager is specified), and the framework
can invoke the profiler during the run (again, akin to how memory manager is handled).

xdje42 added a commit to xdje42/google-benchmark that referenced this issue Jul 1, 2024
This API is akin to the MemoryManager API and lets tools provide
their own profiler which is wrapped in the same way MemoryManager is
wrapped. Namely, the profiler provides Start/Stop methods that are called
at the start/end of running the benchmark in a separate pass.
xdje42 added a commit to xdje42/google-benchmark that referenced this issue Jul 11, 2024
This API is akin to the MemoryManager API and lets tools provide
their own profiler which is wrapped in the same way MemoryManager is
wrapped. Namely, the profiler provides Start/Stop methods that are called
at the start/end of running the benchmark in a separate pass.
xdje42 added a commit to xdje42/google-benchmark that referenced this issue Jul 11, 2024
This API is akin to the MemoryManager API and lets tools provide
their own profiler which is wrapped in the same way MemoryManager is
wrapped. Namely, the profiler provides Start/Stop methods that are called
at the start/end of running the benchmark in a separate pass.
xdje42 added a commit to xdje42/google-benchmark that referenced this issue Jul 16, 2024
This API is akin to the MemoryManager API and lets tools provide
their own profiler which is wrapped in the same way MemoryManager is
wrapped. Namely, the profiler provides Start/Stop methods that are called
at the start/end of running the benchmark in a separate pass.
dmah42 added a commit that referenced this issue Jul 16, 2024
This API is akin to the MemoryManager API and lets tools provide
their own profiler which is wrapped in the same way MemoryManager is
wrapped. Namely, the profiler provides Start/Stop methods that are called
at the start/end of running the benchmark in a separate pass.

Co-authored-by: dominic <510002+dmah42@users.noreply.github.com>
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