Skip to content
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

fix(nvd-mirror): use a more efficient technique to split NVD by year #2517

Merged

Conversation

andrewpollock
Copy link
Contributor

To address apparent overrun issues (and also hopefully reduce the amount of RAM the job requires) use a more time and memory efficient technique to split the monolithic NVD dump by year.

This avoids creating multiple in-memory arrays of the same data

Refactor invocation for better readability

To address apparent overrun issues (and also hopefully reduce the amount
of RAM the job requires) use a more time and memory efficient technique
to split the monolithic NVD dump by year.

This avoids creating multiple in-memory arrays of the same data

Refactor invocation for better readability
Copy link
Member

@michaelkedar michaelkedar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not too familiar with jq but LGTM

@andrewpollock
Copy link
Contributor Author

I'm not too familiar with jq

I've manually built a container and hacked up a Kubernetes job YAML to run it in Staging currently and it is flying along using < 1% of the RAM allocated, by the looks of things :-)

@andrewpollock andrewpollock enabled auto-merge (squash) August 23, 2024 04:49
@andrewpollock andrewpollock merged commit 457cb8c into google:master Aug 23, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants