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
Copy file name to clipboardExpand all lines: docs/graphman.md
+24-8Lines changed: 24 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -371,21 +371,27 @@ Inspect all blocks after block `13000000`:
371
371
372
372
Remove the call cache of the specified chain.
373
373
374
-
If block numbers are not mentioned in `--from` and `--to`, then all the call cache will be removed.
374
+
Either remove entries in the range `--from` and `--to`, remove stale contracts which have not been accessed for a specified duration `--ttl_days`, or remove the entire cache with `--remove-entire-cache`. Removing the entire cache can reduce indexing performance significantly and should generally be avoided.
@@ -404,6 +410,12 @@ the first block number will be used as the starting block number.
404
410
The `to` option is used to specify the ending block number of the block range. In the absence of `to` option,
405
411
the last block number will be used as the ending block number.
406
412
413
+
#### `--remove-entire-cache`
414
+
The `--remove-entire-cache` option is used to remove the entire call cache of the specified chain.
415
+
416
+
#### `--ttl-days <TTL_DAYS>`
417
+
The `--ttl-days` option is used to remove stale contracts based on the `call_meta.accessed_at` field. For example, if `--ttl-days` is set to 7, all calls to a contract that has not been accessed in the last 7 days will be removed from the call cache.
418
+
407
419
### EXAMPLES
408
420
409
421
Remove the call cache for all blocks numbered from 10 to 20:
@@ -412,5 +424,9 @@ Remove the call cache for all blocks numbered from 10 to 20:
0 commit comments