Allow specifying an upper-bound on syncing #84
Replies: 5 comments 1 reply
-
Sounds reasonable. I've seen myself needing this many times while benchmarking. I typically ended up with a custom version of kupo which would just |
Beta Was this translation helpful? Give feedback.
-
As you pointed out in private, this is achievable by turning off pruning, but doing so across the entire network would blow out memory / db, I'm assuming :P |
Beta Was this translation helpful? Give feedback.
-
I am assuming you're indexing everything then?
Memory -> yes. Turning off |
Beta Was this translation helpful? Give feedback.
-
I originally wanted to include this as part of The main question being: is the upper-bound something that is needed once and can be provided on startup only (e.g. |
Beta Was this translation helpful? Give feedback.
-
Addressed by the introduction of pagination which allow setting an upper-bound on queries. Resulting in the desired outcome. |
Beta Was this translation helpful? Give feedback.
-
Describe your idea, in simple words.
Allow a user to specify a maximal point to sync to. After reaching this point, Kupo should stay up and respond to queries, but should not index any additional blocks.
Why is it a good idea?
This would allow users to compute a one-time snapshot of balances across the network, as of a specific slot.
Are you willing to work on it yourself?
Willing? yes, if given a little guidance. ex: Happy to pick it up if someone can point me to another PR that added a command line option, or a link to the region of code where this would need to be modified.
Beta Was this translation helpful? Give feedback.
All reactions