Optimize Necropsy Schedule - #1048
Merged
Merged
Conversation
Contributor
Author
|
I was able to test the query change's performance against the production server. I am not set up to test the UI changes locally against real data, so please test carefully as part of reviewing this PR. |
guyinco6nito
approved these changes
Sep 24, 2026
guyinco6nito
left a comment
Collaborator
There was a problem hiding this comment.
Looks good to me! Please apply this to the EHR-stage server that's currently evaluating LabKey 26.7, we can have the users try it out on that server.
Thanks,
-Dan Metzger
labkey-martyp
approved these changes
Sep 24, 2026
Contributor
Author
|
Merged per guidance from Marty. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
When users rapidly page through months in Necropsy Schedule, it issues separate and moderately expensive queries for each month. That's fine if they only page a few months or page slowly. If they page 30 months with repeated clicks, it's a lot of load for the DB.
Changes