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

EPIC: Reduce dynamic memory use by K_{3,3} search #85

Open
john-boyer-phd opened this issue Jul 10, 2024 · 0 comments
Open

EPIC: Reduce dynamic memory use by K_{3,3} search #85

john-boyer-phd opened this issue Jul 10, 2024 · 0 comments
Labels

Comments

@john-boyer-phd
Copy link
Collaborator

When using the memory checking tool developed for #59, we noted that frequent heap checking (MallocCheckHeapEach set to 6) causes the K_{3,3} search to run substantially slower than the other extensions. This suggests that the implementation uses dynamically allocated memory during its execution. It would be good to look through the code to find those allocations and make some stories here to convert them to allocations during gp_InitGraph() and similar locations so that there is less memory churn during algorithm execution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant