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
There is a suspicion that the integration layer of the node might be invoking computations that are proportional to the type-level lists (TLL) that are used in the hard-fork combinator (HFC).
We need to define a custom Cardano-like era that can be run with our system-level benchmarks so that we can compare its performance with that of the Cardano node.
If there is a cost introduced by the HFC then we want to exaggerate its impact, hence the preference for a long TLL.
The text was updated successfully, but these errors were encountered:
We mostly use strict versions of NS/NP in strict-sop-core, so these would need to be changed in a similar fashion.
This might result in both speed and memory improvements.
A more modest idea is to "reverse" the structure of our NSs such that accessing the most recent era can happen in constant time. See e.g. here for some discussion.
Since CardanoTxOut representation #951, UTxO-HD uses a custom representation for TxOuts (a custom sum type instead of an NS). Maybe the compact representation for NS could make this optimization unnecessary, simplifying the code.
Uh oh!
There was an error while loading. Please reload this page.
There is a suspicion that the integration layer of the node might be invoking computations that are proportional to the type-level lists (TLL) that are used in the hard-fork combinator (HFC).
We need to define a custom Cardano-like era that can be run with our system-level benchmarks so that we can compare its performance with that of the Cardano node.
If there is a cost introduced by the HFC then we want to exaggerate its impact, hence the preference for a long TLL.
The text was updated successfully, but these errors were encountered: