Skip to content
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

Syscalls as nodes in trace tree #88

Open
piotmag769 opened this issue Jun 3, 2024 · 0 comments · May be fixed by #112
Open

Syscalls as nodes in trace tree #88

piotmag769 opened this issue Jun 3, 2024 · 0 comments · May be fixed by #112
Assignees
@THenry14
Labels
design-doc Requires design doc. feature New feature or request.

Comments

@piotmag769
Copy link
Collaborator

As each syscall have a fixed cost, we can present syscalls as separate nodes in the trace tree. Then there will be no need to treat them as separate resources.

We can also consider allowing a users to pass a map with syscall costs, otherwise we would take a default one.
@piotmag769 piotmag769 added feature New feature or request. design-doc Requires design doc. labels Jun 3, 2024
@piotmag769 piotmag769 mentioned this issue Jun 3, 2024
Closed
@THenry14 THenry14 self-assigned this Sep 10, 2024
@THenry14 THenry14 linked a pull request Oct 14, 2024 that will close this issue
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@THenry14 THenry14

Labels
design-doc Requires design doc. feature New feature or request.
Projects
cairo-profiler
Status: In Progress
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Treat syscalls as nodes software-mansion/cairo-profiler
3 participants
@THenry14 @MaksymilianDemitraszek @piotmag769