-
Notifications
You must be signed in to change notification settings - Fork 966
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
Fix Performance of 'by' Operations when verbose=TRUE
#6296
base: master
Are you sure you want to change the base?
Conversation
Generated via commit fc0c1e7 Download link for the artifact containing the test results: ↓ atime-results.zip Time taken to finish the standard R installation steps: 12 minutes and 1 seconds Time taken to run |
@tdhock @Anirban166 I'm trying to run the suite of atime tests locally so I can make sure everything is working before I add a new test, however I'm having trouble with running it based on instructions in https://github.com/Rdatatable/data.table/wiki/Performance-testing I tried to use
Not sure why this is happening, can anyone chime in? |
I created a performance test for this - Result Could probably do with a better/succinct name for the title (open to suggestions) I'm not using a 'Fast' label (as displayed in the latest plot) since it would only exist after this PR is merged onto master here and is available to be installed using the commit SHA associated with it (after this is merged, I can create a follow-up PR for the test). Doesn't seem to be the case where this was previously fast so 'Before' and related labels won't fit. I initially tested 1.15.4 vs 1.15.99 for checking on this - no change (I assume you switched operating systems in between the process of testing other versions yesterday?) so likely not a regression. |
please file an issue with additional details (OS, full input/output, traceback) https://github.com/tdhock/atime/issues |
Yup, I confirmed this here |
Closes #6286
This PR changes calls to C's
clock()
to internalwallclock()
indogroups.c
. Apparently callingclock()
repeatedly on non-Windows platforms used to cause a significant overhead, leading to significantly longer processing times. I found this SO thread that discusses some of the differences between C'sclock()
on different platforms.