-
Notifications
You must be signed in to change notification settings - Fork 15
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
Question(dev): Benchmarking script #76
Comments
Hi @Uzaaft, That's a nice idea! While we have some experience with integration and performance regression testing, we've always done that outside of the context of the code tests themselves (mostly because we were working in C++ and there wasn't an obvious testing framework to use for this purpose). I imagine that some performance tests could be put together using Best, |
I think some "real world" workload, from your guys' own work might perhaps be most applicable. To see what is the slowest parts of the code, etc etc. Again, I'm not a biologist, so I have absolutely no insight whatsoever regarding how you guys work. |
Got it — so I think this would be possible, but would probably require the download of moderately sized external files (stuff that can't easily be put into VC). Presumably there is some standard way to only invoke the tests if the data is present, or to ask to grab the data automatically if the user wants to run these tests. I'm not familiar if there is an idiomatic way to do this in rust or not. |
I think a way could be to cache the data in the /tmp dir, and then make the script look after it there, before it downloads it and caches it again. This way, the data is not saved across reboots(which avoid eating up space), but is there across invocations during a "session". |
For example, the script could be within the |
Hi,
Is it possible to add some kind of benchmarking tests in the test suit, so that one can test for performance regression while implementing changes to the code? I'm not a biologist/gene guy(Just a random HPC enthusiast), so I don't have the brain power to do so myself.
The text was updated successfully, but these errors were encountered: