Skip to content
This repository has been archived by the owner on Sep 22, 2023. It is now read-only.

Look into component memory consumption #26

Open
lulf opened this issue Aug 2, 2023 · 1 comment
Open

Look into component memory consumption #26

lulf opened this issue Aug 2, 2023 · 1 comment
Assignees

Comments

@lulf
Copy link
Contributor

lulf commented Aug 2, 2023

Over time it seems that trustification components will have a high memory usage according to OCP. This task is about finding the cause of that.

@lulf lulf moved this to In Progress in Supply-Chain Trust Manager Aug 2, 2023
@lulf lulf self-assigned this Aug 2, 2023
@lulf
Copy link
Contributor Author

lulf commented Aug 2, 2023

Status:

  • Memory usage is related to the index.
  • Bombastic API and indexer are most heavily affected most likely because of the large objects and index
  • API consumes memory from loading and searching index, not from GET/POST of objects
  • Index size in s3 is 1 GB whereas feeding all documents locally gives a size of 33MB. This seems to be caused by missing garbage collection of old segments.
  • Indexer consumes memory from loading/parsing SBOMs and indexing and also keeping the local index structure in memory

Next steps:

  • Ensure unused segments are garbage collected
  • Look at how to use s3 streaming APIs for storing and loading index.
  • Investigate if index size follows expected size over time if re-feeding the same data many times (no leaks)
  • Experiment with OCP memory limits

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Status: On Hold
Development

No branches or pull requests

1 participant