benchmark

Commit Graph

Author	SHA1	Message	Date
xdje42	ebb5e3922d	Move ProfilerManager Start/Stop routines closer to actual benchmark #1807 (#1818 ) Previously, the Start/Stop routines were called before the benchmark function was called and after it returned. However, what we really want is for them to be called within the core of the benchmark: for (auto _ : state) { // This is what we want traced, not the entire BM_foo function. }	2024-08-01 08:42:41 +01:00
xdje42	7c8ed6b082	[FR] Add API to provide custom profilers #1807 (#1809 ) 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>	2024-07-16 09:56:40 +01:00

Author

SHA1

Message

Date

xdje42

ebb5e3922d

Move ProfilerManager Start/Stop routines closer to actual benchmark #1807 (#1818 )

Previously, the Start/Stop routines were called before the benchmark function
was called and after it returned. However, what we really want is for them
to be called within the core of the benchmark:

  for (auto _ : state) {
    // This is what we want traced, not the entire BM_foo function.
  }

2024-08-01 08:42:41 +01:00

xdje42

7c8ed6b082

[FR] Add API to provide custom profilers #1807 (#1809 )

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>

2024-07-16 09:56:40 +01:00

2 Commits