We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The in-memory cache is great for simple workflows. But for large repositories it usually causes OOM.
A sample repository that was causing OOM was github.com/ApolloAuto/apollo
related issue ossf/scorecard#589
allstar/pkg/ghclients/ghclients.go
Line 83 in 70d3e36
This might not be applicable for allstar but wanted to point out the issues it could run into.
The text was updated successfully, but these errors were encountered:
Thanks, I will do some scale testing with memory size monitoring.
Sorry, something went wrong.
As noted, will keep this in mind. Closing for now. Thanks.
No branches or pull requests
The in-memory cache is great for simple workflows. But for large repositories it usually causes OOM.
A sample repository that was causing OOM was github.com/ApolloAuto/apollo
related issue ossf/scorecard#589
allstar/pkg/ghclients/ghclients.go
Line 83 in 70d3e36
This might not be applicable for allstar but wanted to point out the issues it could run into.
The text was updated successfully, but these errors were encountered: