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
Similar to #17 which is about a more fine-grained performance benchmark for the rpcs, I suggest to do the same for internal functions such as ConnectBlock.
We could either parse the debug log for the durations that are logged or use a more general framework/tooling to collect durations of specific functions or code paths.
The text was updated successfully, but these errors were encountered:
Parsing the debug log sounds like a good first step. I've been kicking around the idea of doing low-frequency callgraph sampling with perf throughout IBD and reindex, so that's another possibility.
I think this would be great -- another benchmark idea I have along these lines is to benchmark the time it takes to call ATMP on a large transaction (both when the inputs are cached and when they aren't, and when the transaction's scripts are valid and when they're not, due to a policy reason).
Similar to #17 which is about a more fine-grained performance benchmark for the rpcs, I suggest to do the same for internal functions such as
ConnectBlock
.We could either parse the debug log for the durations that are logged or use a more general framework/tooling to collect durations of specific functions or code paths.
The text was updated successfully, but these errors were encountered: