-
Notifications
You must be signed in to change notification settings - Fork 25
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
fix(form): optimize calculated question performance #2339
Conversation
czosel
commented
Dec 2, 2024
•
edited
Loading
edited
- drop several signals in favor of explicit calls in domain logic to allow reuse of form structure
- add prefetching for document structure
- apply topological sorting before calculating answers on document creation
@czosel Note: Instance creation is still slow, and seems to be triggered by create in SaveDocumentLogic. I'm having a look. |
Form changes (e.g. through form-builder) are probably also still slow. |
a47c6e1
to
33746a0
Compare
4584728
to
d1bd793
Compare
d1bd793
to
ad4d2e7
Compare
0426441
to
af7e014
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work so far! Not sure we're all the way there yet tho :-)
3ba8809
to
0788067
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work so far, just a few suggestions
2fecfe2
to
a5eb854
Compare
This sorts the graph that is formed by calculated questions and their dependents, and then initializes them in the correct order.
1d879c7
to
dc0e4eb
Compare
@winged I think we should squash this on merge. I enabled squashing in the repo settings, just not sure if it'll mess up the commit message. |