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

Feature Request: Option to enable benchmarking on pipes #16

Open
latot opened this issue Nov 14, 2023 · 1 comment
Open

Feature Request: Option to enable benchmarking on pipes #16

latot opened this issue Nov 14, 2023 · 1 comment

Comments

@latot
Copy link

latot commented Nov 14, 2023

Hi all!, I really like this lib, I practically replaced magrittr with it.

Now, after some time playing and everything, I think is very important in languages like R be able to know the timing on the lines.

R is not "uniform", has a lot of operations where you change a little how to do something and impact a lot on the performance.

So, I was thinking would be great, a way to get the benchmarks, get the time of every line, would be great so measure performance and know which lines took more time to focus on improve the code.

I was thinking like:

options(wrapr_pipe_benchmark = TRUE)

This is the basis of the idea, there is still some points.

  • How to collect/show the data
  • There must be a way to handle deep, benchmarks on one function, more functions, per function

I know in order for a full benchmark, there is one missed point, and is create an operator to replace <- to handle a similar behavior, but, we can also do funny things like f(x) %.>% . and get the same values :3

Thx!

@JohnMount
Copy link
Member

Thanks for your kind words.

I understand your ask, you want to profile the pipe stages (not the pipe operator itself). Probably something I can think about, but I don't have a lot of resources I can commit to that in the short term.

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

2 participants