Track memory usage during qlever index#277
Open
tanmay-9 wants to merge 17 commits intoqlever-dev:mainfrom
Open
Track memory usage during qlever index#277tanmay-9 wants to merge 17 commits intoqlever-dev:mainfrom
qlever index#277tanmay-9 wants to merge 17 commits intoqlever-dev:mainfrom
Conversation
tanmay-9
changed the title
qlever index commandqlever index command
…/podman different memUsage parsing
tanmay-9
changed the title
qlever index commandqlever index
…e to the plot. Also make gb use consistent
…u cores used and add downsampling (max_points=500) for plot
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
1 participant
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.
qlever indexnow monitors memory usage of the index-building process in the background and logs peak memory at the end.qlever.<dataset>.memory-log.jsonfile is written to the working directory with timestamped RSS samples and peak usage.psutil) and containerized mode (viadocker stats/podman stats).qlever-control, each engine's indexing will produce its own memory log in the same format. These can be compared side-by-side using the evaluation web app to visualize memory usage differences across engines and datasets.