Repository navigation
Conversation
Yano's catch-up placed one empty block per slot, so create time grew with epoch length and the relay had to copy the whole chain. A relay only needs one block per stability window (3k/f) to validate the history. - add yano.backfill.block.interval.slots (auto: a quarter of 3k/f, an integer to force, 1 for one block per slot) - pass it to Yano as yano.block-producer.backfill-block-interval-slots in past-time-travel mode, through the environment and the properties file - document it in the node modes page and the CLI properties file Needs a Yano build that knows the property; older builds ignore it.
8 of 12 tasks
Member
|
This one is superseded by #193, which is now merged, so I'm closing it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Yano's catch-up from the shifted genesis to wall clock places one empty block per slot, so create time grows with epoch length and the relay must copy the whole chain (about 550 blocks/s measured). A Haskell relay only needs one block per stability window (3k/f) to validate the history.
yano.backfill.block.interval.slots: auto(default) derives a quarter of the stability window3k/ffrom the cluster'skandactiveSlotsCoeff; an integer forces it; 1 keeps one block per slotyano.block-producer.backfill-block-interval-slots, through the environment and Yano's properties file; nothing is passed when the result is 1applications/cli/config/application.properties; unit tests cover the derivation and the overridesDepends on bloxbean/yano#124 (
yano.block-producer.backfill-block-interval-slots). Until the DevKit pins a Yano release that carries that property, this change has no effect: the bundled 0.1.0-pre6 starts cleanly with the property set and ignores it (verified against the beta5 image). It can merge before or after that release; it only becomes active with the pin bump. AtactiveSlotsCoeffbelow 1 the property also needs bloxbean/yano#125, since the slot-leader shift fails on Yano main before catch-up without it.Measured with a Yano build from bloxbean/yano#124 and #125: a devnet with 3s blocks on 1s slots and 14-day epochs (k 80640, 3k/f 725760 slots) caught up 3,628,800 slots in 26 blocks, the relay accepted them all, PV11 cost models were enacted (332/332/350), and the whole create took under two minutes. With 7s blocks and 6-day epochs the same run placed 24 blocks. Create time no longer depends on epoch length.