-
Notifications
You must be signed in to change notification settings - Fork 39
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
Reduce number of (re)allocations #17
Comments
@Nashtare Can you elaborate a bit on what kind of allocation strategy you would like to see here, or point to examples in the code where you'd like to see refactorings? As it stands the description is a bit vague. |
There are a few TODOs / collect that could be modified, though I mostly put it as a tracking ticket, following an offline discussion with @BGluth |
Yeah just to add, there are a handful of unnecessary heap allocations (IIRC mostly to deal with some lifetime issues), but I would expect only extremely negligible performance improvement after dealing with all of them. It might be more to just make the codebase cleaner, since we spend almost all of our time inside |
Yeah I also think it's nice to reduce these AMAP, even though they aren't performance critical compared to the prover. I also have a WIP branch for this purpose on the plonky2 side. |
AMAP? You mean ASAP? |
As much as possible :) But it could also be ASAAMAP combining both :D |
TIL! |
There are several allocations / reallocations across the decoder that could probably be alleviated with some refactoring.
To be tackled after #19 probably...
The text was updated successfully, but these errors were encountered: