Performance and quality assurance strategy

[amani-es]

Why

Quoting the opening section Implementation imperatives of the technical design created in #542:

In summary, the technical design described in subsequent chapters must ensure that nodes continue to operate reactively and meet timing requirements despite increased responsibilities and data volumes. This requires careful bounding of resource usage and sophisticated prioritization mechanisms across concurrent responsibilities.

The complexity of this challenge emphasizes the critical importance of non-functional requirements specification for each component, rigorous performance engineering practices, and continuous benchmark validation throughout the development process. Only through systematic attention to these implementation details can the protocol deliver the security and performance properties that make Leios a valuable enhancement to Cardano's capabilities.

What

Incorporate latest understanding on what kind of benchmarking or testing we would like to see across the respective components, on a whole node-integration or cluster-integration level.

How

The leios-design document provides ample opportunity to expand on these points in the implementation plan, risks & mitigations or technical design chapters.

Possible steps:

• Update implementation plan as needed
• Expand on key threats or things to validate early
• Adapt/replace testing and benchmarking sections in technical design (current content taken from early Impact analysis document #546 work)

[ch1bo]

Merged with a draft item we had on this already and scoped it to the best of my knowledge. @mgmeier @mkoura what's your take on this?

[ch1bo]

Write about topics you pitched @mgmeier:

• Tracing to support trace verification (with the right semantics)
• Creating interesting test data that saturates (extrapolating activity)
• Collaboration with formal methods on linear temporal logic (alternative to agda model) cc @ramsay-t