✨ Support API rendering of large collections with MUCH less memory. #822
Conversation
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
Signed-off-by: Jeff Ortel <[email protected]>
Signed-off-by: Jeff Ortel <[email protected]>
Signed-off-by: Jeff Ortel <[email protected]>
jortel
changed the title
jortel
added a commit
that referenced
this pull request
May 27, 2025
Query the application using joins instead of preload() and the response streamed back with in-line encoding. Much faster. Reduces query of 5k applications from 10-14 seconds to 3-4 seconds. Also keeps RSS (memory) to around 100-130 MB instead of ballooning to 6-7GB and staying there. Tested on minikube with SSD storage. The assessment package need to be changed so that the resolvers ALL could be built upfront to ensure no other SQL statements were executed while iterating the cursor (which holds the db lock). Overlaps with #822: - api/context.go - api/analysis.go After #822 is merged, these files will need to be unstaged and the PR rebased. Signed-off-by: Jeff Ortel <[email protected]>
This was referenced Jul 16, 2025
This was referenced Aug 22, 2025
This was referenced Sep 8, 2025
This was referenced Sep 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Moves SAX-like encoders to from analysis.go to context.go for more general usage.
Using these encoders instead of standard json|yaml encoders for large arrays GREATLY reduce memory footprint.
Add (cursor) Iterator to better support queries using joins instead of pre-loading. The iterator groups rows (by ID) into batches. Joins return a flattened object graph. Each batch is passed to the supplied Builder function to construct the resource.
Note:
In Java, SAX stands for Simple API for XML.
It is a stream-based, event-driven API used for parsing XML documents. Unlike DOM parsers, which load the entire XML document into memory as a tree, SAX parsers read the XML document sequentially and trigger events as elements are encountered, making them faster and more memory-efficient, especially for large XML files.