Closed mrchypark closed 5 years ago
Thanks for filling this suggestion. The only problem now about dtplyr is that it is not actively maintained. There are few commits in February but not really what is required there. As of now it make sense to run it once to see how it performs but doesn't make sense to have that in benchmark scheduler.
Make sense. Thank you for consider this option.
best will be to get back to this when dtplyr will be maintained again
dtplyr is actively maintained again. Although I don't think so we should be adding it to benchmark. We could assume it will be similarly fast as data.table. We don't want to benchmark translation layer (which dtplyr is) but algorithm implementations. Otherwise it would also make sense to add sparklyr, spark from scala, etc.
How about dtplyr?
dtplyr package provide function that can use dplyr syntax with data.table class.
https://github.com/hadley/dtplyr