Skip to content

Leios design: Perf & Tracing #596

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Leios design: Perf & Tracing #596

wants to merge 1 commit into from

Conversation

@mgmeier
Copy link
Contributor

@mgmeier mgmeier commented Oct 27, 2025

This PR contributes to #542 .

@mgmeier mgmeier mentioned this pull request Oct 27, 2025
Open
12 tasks
@ch1bo ch1bo changed the title Leios Design - Perf & Tracing Leios design: Perf & Tracing Oct 27, 2025
@ch1bo ch1bo linked an issue Oct 27, 2025 that may be closed by this pull request
Write technical design and implementation plan #542
Open
12 tasks
@ch1bo ch1bo self-requested a review October 27, 2025 11:01
ch1bo
ch1bo reviewed Oct 27, 2025
View reviewed changes
Copy link
Member

@ch1bo ch1bo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mgmeier Do you see P&T as an aspect of the design (a dedicated area/layer or relevant across all concerns?), or something we should elaborate on in the #592.

docs/leios-design/README.md
As Leios development in all aspects is an ongoing and very much alive process, this chapter could only focus on
mid-to-high-level items. Depending on the progress of various protoypes and implementations, this high-level plan
will need to be broken down and sequenced into smaller tasks. We will do so keeping in mind the result of those
tasks should be reusable both internally, and by the community.
Copy link
Member

@ch1bo ch1bo Oct 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How should this relate to the implementation plan chapter (#592)?

@mgmeier
Copy link
Contributor Author

mgmeier commented Oct 28, 2025 •
edited
Loading

Generally, the issue this PR targets addresses "technical design and implementation plan" - so this contribution contains a bit of both. I'd be fine though with moving the contribution to issue #592.
P&T work on Leios is by nature less geared towards design questions.

@ch1bo
Copy link
Member

ch1bo commented Oct 29, 2025

Generally, the issue this PR targets addresses "technical design and implementation plan" - so this contribution contains a bit of poth. I'd be fine though with moving the contribution to issue #592. P&T work on Leios is by nature less geared towards design questions.

As discussed, let's incorporate the great points of this PR into respective sections next month - once the dust on the initial scaffold settles (the many in flight PRs onto #542).

@ch1bo ch1bo self-assigned this Oct 29, 2025
@ch1bo ch1bo marked this pull request as draft October 29, 2025 08:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ch1bo ch1bo ch1bo left review comments

Assignees

@ch1bo ch1bo

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Write technical design and implementation plan

3 participants

@mgmeier @ch1bo