tracing: correctly scope utxocache:flush tracepoint
Previously, the `utxocache:flush` tracepoint was in the wrong scope and reached every time `CChainState::FlushStateToDisk` was called, even when there was no flushing of the cache. The tracepoint is now properly scoped and will be reached during a full flush. Inside the scope, the `fDoFullFlush` value will always be `true`, so it doesn't need to be logged separately. Hence, it's dropped from the tracepoint arguments.
This commit is contained in:
1 parent
5d91133699
commit
36a6584703
4 files changed
+16
-35
No files matched your search
@@ -237,7 +237,7 @@ Histogram of block connection times in milliseconds (ms).
|
||||
|
||||
### log_utxocache_flush.py
|
||||
|
||||
A BCC Python script to log the cache and index flushes. Based on the
|
||||
A BCC Python script to log the UTXO cache flushes. Based on the
|
||||
`utxocache:flush` tracepoint.
|
||||
|
||||
```bash
|
||||
@@ -246,23 +246,10 @@ $ python3 contrib/tracing/log_utxocache_flush.py ./src/bitcoind
|
||||
|
||||
```
|
||||
Logging utxocache flushes. Ctrl-C to end...
|
||||
Duration (µs) Mode Coins Count Memory Usage Prune Full Flush
|
||||
0 PERIODIC 28484 3929.87 kB False False
|
||||
1 PERIODIC 28485 3930.00 kB False False
|
||||
0 PERIODIC 28489 3930.51 kB False False
|
||||
1 PERIODIC 28490 3930.64 kB False False
|
||||
0 PERIODIC 28491 3930.77 kB False False
|
||||
0 PERIODIC 28491 3930.77 kB False False
|
||||
0 PERIODIC 28496 3931.41 kB False False
|
||||
1 PERIODIC 28496 3931.41 kB False False
|
||||
0 PERIODIC 28497 3931.54 kB False False
|
||||
1 PERIODIC 28497 3931.54 kB False False
|
||||
1 PERIODIC 28499 3931.79 kB False False
|
||||
.
|
||||
.
|
||||
.
|
||||
53788 ALWAYS 30076 4136.27 kB False False
|
||||
7463 ALWAYS 0 245.84 kB False False
|
||||
Duration (µs) Mode Coins Count Memory Usage Prune
|
||||
730451 IF_NEEDED 22990 3323.54 kB True
|
||||
637657 ALWAYS 122320 17124.80 kB False
|
||||
81349 ALWAYS 0 1383.49 kB False
|
||||
```
|
||||
|
||||
### log_utxos.bt
|
||||
|
||||
Reference in new issue
Block a user