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.

Sign up for GitHub

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

Jump to bottom

Use PROOF to speed up cutapplier #6

Open
admorris opened this issue Jan 25, 2018 · 2 comments
Open

Use PROOF to speed up cutapplier #6

admorris opened this issue Jan 25, 2018 · 2 comments

Comments

@admorris
Copy link
Contributor

I noticed this mentioned on the Mattermost (Example). Doesn't seem too complicated to implement but I don't have time immediately, so I'm making this issue to remind myself.
@admorris
Copy link
Contributor Author

It's more complicated than I thought. Apparently you have to write a whole TSelector class just to apply a cut in parallel?

@cofitzpa
Copy link
Owner

I always assumed the bottleneck for cutapplier was the I/O rather than the CPU, so never investigated using PROOF for it. The place where parallelisation would be handy is in crop and bwdiv imo. I've already parallelised bwdiv in a private version using TProcessExecutor and that works very nicely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cofitzpa @admorris