Skip to content
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

case_when is very slow in version 1.1.0 #6788

Closed
rszulkin opened this issue Mar 14, 2023 · 6 comments
Closed

case_when is very slow in version 1.1.0 #6788

rszulkin opened this issue Mar 14, 2023 · 6 comments

Comments

@rszulkin
Copy link

Hi,

I don't know if this has been reported already but I experience the same thing as in this stackoverflow post. The case_when funciton has become extremly slow in this new version

https://stackoverflow.com/questions/75304966/dplyr-v1-1-0-runtime-much-slower-for-case-when-with-grouping-variable

Kind regards,
Robert

@bevthewitch
Copy link

Hi Robert, yes I'm experiencing a significant slow-down and have been testing different versions of dplyr. Previously my code ran in seconds, now it takes 10 minutes!

@rszulkin
Copy link
Author

Hi Robert, yes I'm experiencing a significant slow-down and have been testing different versions of dplyr. Previously my code ran in seconds, now it takes 10 minutes!

OK! It's the same on my computer. Seems to be a common problem then.

@joranE
Copy link
Contributor

joranE commented Mar 14, 2023

Previously discussed at length (and I believe addressed in the dev version) here.

@rszulkin
Copy link
Author

Previously discussed at length (and I believe addressed in the dev version) here.

Thank you!

@bevthewitch
Copy link

bevthewitch commented Mar 14, 2023

I wasn't sure if it was the case_when or my lags that were the problem, but it is a significant slowdown over 60500 records. At least it has been recognised and I'm not the only one experiencing this.

We've also just moved from R Studio Server Pro to Posit Workbench, and had access to a more recent version of R so it was complicated teasing out what was causing the problem.

@DavisVaughan
Copy link
Member

We've basically fixed this in the dev version, which should go to CRAN in a week or so, with additional plans to make it faster in the future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants