Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Ideal memory requirement for NameRes on Translator #152

Open
gaurav opened this issue Jul 1, 2024 · 2 comments
Open

Ideal memory requirement for NameRes on Translator #152

gaurav opened this issue Jul 1, 2024 · 2 comments

Comments

@gaurav
Copy link
Contributor

gaurav commented Jul 1, 2024

Some numbers on this issue:

  • We have NameRes Solr set up with both a memory request and memory limit of 58Gi on both RENCI (Dev) and ITRB (CI, Test, Prod)
  • Solr itself reports approx 2.30GB/58.00GB of JVM Memory used and 13.83GB/58.00GB of physical memory in normal use, but peaking at 26.61GB when running the babel-validation test suite.
  • Kubernetes shows memory usage of 7.11Gi (WSS), 7.00 GiB (RSS) and 15.88 GiB (Cache), even when running the babel-validation test suite.

We are getting CPU-limited, so I'm going to try to increase our CPU limit first, and then see if we need to increase our memory limit.

@gaurav
Copy link
Contributor Author

gaurav commented Jul 1, 2024

This time we peaked at 2.57 CPUs, which means we had very slight (2%) of CPU throttling. Memory usage peaked at 6.83 GiB (WSS). However, we still had four requests time out. I should try to increase CPUs to e.g. 5 and see if that fixes it; otherwise, there might be some kind of Solr config we need to tweak.

@gaurav
Copy link
Contributor Author

gaurav commented Oct 15, 2024

See helxplatform/translator-devops#983 for some work on this.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant