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

Consider storing the profile aggregation in the constraints data frames (or somewhere else) #473

Open
abelsiqueira opened this issue Feb 15, 2024 · 2 comments
Labels
Type: improvement Better way of doing something Zone: code architecture Changes to the structure or fundamentals

Comments

@abelsiqueira
Copy link
Member

What and Why

Right now, we use the function profile_sum (and friends) to compute the profile sum. It might be faster to store it into a dataframe (or somewhere else).
It should be easier to evaluate this after #344.

Possible Drawbacks

It might use more memory.

Related Issues

No response

@abelsiqueira abelsiqueira added the Type: improvement Better way of doing something label Feb 15, 2024
@clizbe clizbe added the Zone: code architecture Changes to the structure or fundamentals label Feb 19, 2024
@abelsiqueira
Copy link
Member Author

Better to wait until #456

@clizbe
Copy link
Member

clizbe commented Apr 22, 2024

Wait for #547

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: improvement Better way of doing something Zone: code architecture Changes to the structure or fundamentals
Projects
None yet
Development

No branches or pull requests

2 participants