Add overview of the tasks of a caught-up node #1215
Conversation
amesgen
added
documentation
amesgen
force-pushed
the
amesgen/node-tasks-overview
branch
3 times, most recently
from
5c30a4f to
0572d0b
Compare
amesgen
requested review from
nfrisby,
jasagredo,
fraser-iohk,
dnadales and
RenateEilers
as code owners
amesgen
force-pushed
the
amesgen/node-tasks-overview
branch
from
0572d0b to
75dfc10
Compare
| VolatileDB --> CopyToImmutableDB | ||
| CopyToImmutableDB --> ImmutableDB | ||
| GarbageCollect -- "cleans up" --> VolatileDB | ||
| LedgerDB --> CreateLedgerSnapshot |
There was a problem hiding this comment.
This looks like it is aligned with the ImmutableDB, but it should be aligned with the volatiledb. Maybe it is not possible with mermaid?
There was a problem hiding this comment.
Yeah, I don't think Mermaid has enough flexibility for stuff like this. Maybe it is possible to do sth with invisible arrows, but I don't think it is too terrible.
amesgen
force-pushed
the
amesgen/node-tasks-overview
branch
from
75dfc10 to
0b3adba
Compare
|
|
||
| 7. In parallel, chain selection for B continues by validating B. | ||
|
|
||
| Time budget: average ~30ms, upper bound ~500ms. |
There was a problem hiding this comment.
Where does 500ms come from? EG the June attack exceeded this -- what's the scope being considered here? Perhaps it's none-buggy-block validation 😬
There was a problem hiding this comment.
Thanks for pointing that out, I chose that number somewhat arbitrarily. According to the recent db-analyser pass, there are only 1596 blocks with block application mutator time higher than 500ms, out of which 1574 (all but 22 blocks) are due to the ref script DoS.
I added a "based on empirical data" caveat.
amesgen
force-pushed
the
amesgen/node-tasks-overview
branch
from
0b3adba to
e290eed
Compare
amesgen
force-pushed
the
amesgen/node-tasks-overview
branch
from
e290eed to
d594504
Compare
amesgen
force-pushed
the
amesgen/node-tasks-overview
branch
from
d594504 to
562071e
Compare
Closes #1057