You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, I noticed that the performance of collapse::fsd() seems to have gone down on a little benchmark I've been running between versions 2.0.15 and 2.0.16. I tried a few combinations of R and and collapse going back to 4.2.1 and 1.8.9 respectively and I think the issue stems from collapse. This is the script I've been testing with:
The plain fsd() call went from 12ms to 27ms, and the smr(x = fsd(x)) went from 12ms to 48ms. A different test with fmean() showed no differences there, but I didn't try any of the other special fast statistical functions outside of those two.
Just thought I'd flag the issue since it seems it hasn't been noticed yet and I didn't see anything the seemed like it could be related in the NEWS for 2.0.16. I wish I could offer more to identify the root issue but it's beyond my capabilities I think.
The text was updated successfully, but these errors were encountered:
Thanks @andrewGhazi, I'll look into this as I find time! In general though if you want speedy standard deviations, do use the option stable.algo = FALSE to fsd(). You can also set it globally using set_collapse().
Hi there, I noticed that the performance of
collapse::fsd()
seems to have gone down on a little benchmark I've been running between versions 2.0.15 and 2.0.16. I tried a few combinations of R and and collapse going back to 4.2.1 and 1.8.9 respectively and I think the issue stems from collapse. This is the script I've been testing with:On the
rocker/r-ver:4.4.2
image with[email protected]
that script produces:But the same script on the same image with
[email protected]
yields:The plain
fsd()
call went from 12ms to 27ms, and thesmr(x = fsd(x))
went from 12ms to 48ms. A different test withfmean()
showed no differences there, but I didn't try any of the other special fast statistical functions outside of those two.Just thought I'd flag the issue since it seems it hasn't been noticed yet and I didn't see anything the seemed like it could be related in the NEWS for 2.0.16. I wish I could offer more to identify the root issue but it's beyond my capabilities I think.
The text was updated successfully, but these errors were encountered: