-
Notifications
You must be signed in to change notification settings - Fork 17
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
Enhancement possibility? --> Pipe cache #14
Comments
It might be possible. It still wouldn't be as fast as doing it manually, because there would be some overhead of creating a key and looking it up in the cache. Also it's quite easy to do it explicitly as in your |
It would be nice if there was a way to do incremental data analysis where intermediate results could be cached and checked/viewed. For example,
Then hit "up-arrow" on the keyboard and just add the next transformation/aggregation at the end of the previous line...
... where Is there an easy way to do this without manually storing intermediate analysis results? |
Well that's another story - I thought you only wanted to cache the pipe itself, not the result of calling it. For this you'd have to make some sort of Also there's usually some sort of magic variable, in case of IPython it's In [6]: big_data_list > pipe | transformation_that_takes_a_long_time
...
In [7]: _ > pipe | another_long_transformation # or another_long_transformation(_)
... Which might be a decent workaround for you. |
There is some overhead to create pipes. For some use cases it may be advantageous to cache pipes or even partial pipes. Would it be possible to cache pipes automatically? ... or by some switch, etc.?
Here you can see the "penalty" associated with creating pipes.
The text was updated successfully, but these errors were encountered: