-
Notifications
You must be signed in to change notification settings - Fork 10
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
Reduce runtime of gridding tests #225
Comments
Woah, what is taking so long? The wgridder tests run in just under a minute on my laptop which I don't think is that bad |
It's not a train smash because comprehensive tests are a good thing and it's better to have long-running test cases than not. Also, I think a minute is reasonable for a set of functionality. Looking towards the future, the test suite is only going to take longer so its worthwhile considering how to pare its run time down. |
My tests run in under 5 minutes on my desktop, primarily due to the
computation of the DFT
272.85s user 6.62s system 115% cpu 4:01.33 total
I guess we can cache this as a numpy array somewhere and download it to
speed it up? The actual gridding/degridding time is well under a minute in
total.
…On Wed, Sep 23, 2020 at 3:59 PM Landman Bester ***@***.***> wrote:
Woah, what is taking so long? The wgridder tests run in just under a
minute on my laptop which I don't think is that bad
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#225 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4RE6VQFNEE67CESFYKBI3SHH5LVANCNFSM4RXCGPQQ>
.
--
--
Benjamin Hugo
PhD. student,
Centre for Radio Astronomy Techniques and Technologies
Department of Physics and Electronics
Rhodes University
Junior software developer
Radio Astronomy Research Group
South African Radio Astronomy Observatory
Black River Business Park
Observatory
Cape Town
|
Is it now possible to just make tests that need the DFT smaller? |
I've halved my runtime. If further optimization is needed I can cache the dft between test cases. |
This is quite doable with a pytest fixture. |
It appears that is deprecated (pytest-dev/pytest#3118) I will need to dump it into a file somewhere |
Description
We've got two new gridders which is great. However, the test suite runtime has increased I guess by a third -- we're now looking at ~18 minutes for testing a single commit. Would it be possible to reduce the data sizes of some of these cases, without losing accuracy?
The text was updated successfully, but these errors were encountered: