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

optimise memory usage in perturbator computation #745

Open
maramihali opened this issue Oct 7, 2023 · 2 comments
Open

optimise memory usage in perturbator computation #745

maramihali opened this issue Oct 7, 2023 · 2 comments
Assignees
Milestone

Comments

@maramihali
Copy link
Contributor

No description provided.

@maramihali maramihali added this to the Protogalaxy milestone Oct 7, 2023
@lucasxia01
Copy link
Contributor

lucasxia01 commented Feb 15, 2024

could do this at some point. Should be able to multithread at each level pretty easily and also reduce memory consumption by doing this iteratively/reusing the same vector of vectors.

although not sure how impactful this would be since the perturbator now accounts for a relatively low percentage of folding

@maramihali maramihali self-assigned this Nov 14, 2024
@codygunton codygunton mentioned this issue Feb 27, 2025
7 tasks
@maramihali
Copy link
Contributor Author

I had an attempt at this while doing various optimisations around the structure trace (moving from a 2D array to a 1D array and building the coefficient tree in-place), it makes parallelisation trickier and since the perturbator is not a memory bottleneck maybe, there is no need for the optimisation.

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

No branches or pull requests

2 participants