I'm afraid this is difficult to reproduce without profiling at different versions, but I wanted to give an anecdotal heads-up about performance issues I encountered after updating to the most recent version of R and updating all of my tidyverse packages on a new machine.
On my machine, this code block takes 100ms for nboot=10, 29,270ms for nboot=100, 107,750ms for nboot=200, and so on.
I profiled the code, and it looks like essentially all of the time is spent in the tidyr::unnest function, specifically the unchop function... I know this took a major performance hit in the tidyr 1.0.0 update, but even after updating to tidyr 1.1.0, where they included a number of performance improvements to unnest, it's still pretty slow.
Do you think it would possible to work around this in tidyboot? I wondered even if switching back to the unnest_legacy function would help, if the fancier new interface for unnest isn't strictly necessary?
I'm afraid this is difficult to reproduce without profiling at different versions, but I wanted to give an anecdotal heads-up about performance issues I encountered after updating to the most recent version of R and updating all of my
tidyverse
packages on a new machine.On my machine, this code block takes 100ms for
nboot=10
, 29,270ms fornboot=100
, 107,750ms fornboot=200
, and so on.I profiled the code, and it looks like essentially all of the time is spent in the
tidyr::unnest
function, specifically theunchop
function... I know this took a major performance hit in the tidyr 1.0.0 update, but even after updating to tidyr 1.1.0, where they included a number of performance improvements tounnest
, it's still pretty slow.Do you think it would possible to work around this in
tidyboot
? I wondered even if switching back to theunnest_legacy
function would help, if the fancier new interface forunnest
isn't strictly necessary?