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
Performance test data #1106
Performance test data #1106
Conversation
@@ -65,10 +67,20 @@ | |||
:application/form | |||
:application/licenses)) | |||
|
|||
(mount/defstate all-applications-cache | |||
:start (atom {:last-processed-event-id 0 | |||
:applications nil})) |
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.
core.cache has nice functional caches with various startegies... would they be applicable?
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.
The events are immutable and the injections are not yet cached in state, so for now an atom is enough. I'll keep core.cache in mind when doing further optimizations.
The following tests are coupled to the amount of test data and would break: rems.migrations.test-convert-to-dynamic-applications/test-migration rems.api.test-catalogue-items/catalogue-items-api-test
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.
some suggestions ... otherwise fine
#863
The most critical performance optimizations have been done. More will follow.