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.

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

Eliminate copy of graph objects to improve memory utilization #166

Open
msschwartz21 opened this issue Nov 7, 2024 · 1 comment
Open
Labels
bug Something isn't working performance Changes that impact runtime and performance

Comments

@msschwartz21
Copy link
Collaborator

There are at least two places where we create copies of the TrackingGraph:

  • At the initialization of the Matcher
  • When correcting shifted divisions

We should eliminate both of these instances. The first is easy, but the second may require more thought since we are essentially putting duplicate labels on the graph.

@msschwartz21 msschwartz21 added bug Something isn't working performance Changes that impact runtime and performance labels Nov 7, 2024
@msschwartz21
Copy link
Collaborator Author

#74 eliminated the copy of the graph that was created by the matcher, but copies are still created during correcting division frame shift errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working performance Changes that impact runtime and performance
Projects
Status: No status
Development

No branches or pull requests

1 participant