On Mon, 21 Aug 2023 13:28:54 +0100 Scott Ritchie <sritchi...@gmail.com> wrote:
> Examples with CPU time > 2.5 times elapsed time > user system elapsed ratio > remove_technical_variation 2.603 0.027 0.94 2.798 In this context, "user" means the time spent executing userspace code (as opposed to work done on behalf of the process by the operating system kernel, "system"), and "elapsed" is the real time. Some threads or child processes are definitely at work here. Dirk is probably right that it's a good idea to have OMP_THREAD_LIMIT=2 set on the CRAN check machine. Either that, or place the responsibility on data.table for setting the right number of threads by default. But that's a policy question: should a CRAN package start no more than two threads/child processes even if it doesn't know it's running in an environment where the CPU time / elapsed time limit is two? -- Best regards, Ivan ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
