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

Add stress tests #277

Open
gaurav opened this issue Jul 5, 2024 · 0 comments
Open

Add stress tests #277

gaurav opened this issue Jul 5, 2024 · 0 comments

Comments

@gaurav
Copy link
Contributor

gaurav commented Jul 5, 2024

We sometimes run into issues that show up only when NodeNorm is being strained (e.g. #276, #175). We should write some tests designed to stress NodeNorm out. Ideally this could be added to the integration tests in Babel Validation (https://github.com/TranslatorSRI/babel-validation), but if not we should at least add them to Yaphet's Predator instance.

One of the issues here is that Redis tends to cache requests, so we can't use anything from the existing Babel test results that are part of the integration tests, nor can we use a fixed list that we can test repetitively. Given that we're just trying to evaluate NodeNorm's networking and database lookup capabilities, it might be enough to create a test that generates a large number of random CURIEs (randomly chosen prefix from https://nodenormalization-sri.renci.org/1.5/get_curie_prefixes + random number with a mean somewhere in the 100s but a long tail into the 10,000s).

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

No branches or pull requests

1 participant