Simple Engine profiling #7
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: SeanOMik/lyra-engine#7
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The engine is already using tracing as a logging library, however it can also be used as an instrumentation tool.
The plan I have is to use the
#[instrument]proc-macro in more places in the engine, and manually create spans wherever they are needed. There is a great tool called Tracy that can be used to view the profile. The tracing_tracy library is required to collect Tracy profiles from tracing instrumentation. There's also clippy-tracing that can be used to add the instrument attribute to all functions automatically.Profiling the engine using Tracingto Engine profilingEngine profilingto Simple Engine profilingThe profiling tools above have been implemented and tested. They work great. It will take some time to profile the entire engine, each portion can be instrumented when each part is being worked on. I think its safe to close this, even if the entire engine isn't profiled.