...
Then you run a benchmark that executes the desired code multiple times, enough to fill up the circuit the circular buffer. Once the benchmark has run, you can print out the buffer to the log using the printToLog method, like this:
No Format | ||
---|---|---|
| ||
context->printToLog(); |
From the information that's printed you can identify the places where the most time is being spent, and then add additional calls to TimeTrace to divide up the large blocks of time. Eventually you should be able to figure out exactly where all the time is going. If the recording is happening on a RAMCloud server but you are running a benchmark from a client machine, you can invoke the a ServerControl RPC on the client to ask the server to dump its time trace buffer to the log:
...