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

Investigate removing allocation during collection #22

Open
Others opened this issue May 21, 2020 · 0 comments
Open

Investigate removing allocation during collection #22

Others opened this issue May 21, 2020 · 0 comments
Labels
T-optimization Something is slower than it needs to be

Comments

@Others
Copy link
Owner

Others commented May 21, 2020

Currently we use two vectors in collection (which is better than the many vectors we used before). One is used for root-tracking/DFS (depth first search) and the other stores the lockout items. These vectors are potentially massive, so we probably want to investigate how to get rid of them, probably by using an intrusive linked list somehow
@Others Others added the T-optimization Something is slower than it needs to be label Jun 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-optimization Something is slower than it needs to be
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Others