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

Better piping #1

Open
BookOwl opened this issue Mar 27, 2017 · 2 comments
Open

Better piping #1

BookOwl opened this issue Mar 27, 2017 · 2 comments
Assignees
@BookOwl
Labels
enhancement
Milestone
v1.0

Comments

@BookOwl
Copy link
Owner

BookOwl commented Mar 27, 2017 •
edited

Currently nemo uses threads and queues to implement piping. This isn't a very good solution for several reasons.

  1. Threads are heavy, and spawning a new thread for each part of a pipeline can't be very efficient.
  2. The order different parts of the pipeline are run in can't be controlled.

A single threaded solution would be much better. I've tried coroutines, but I can't get the code to work right without segmentation faults.
@BookOwl BookOwl self-assigned this Mar 27, 2017
@BookOwl BookOwl added this to the v1.0 milestone Mar 27, 2017
@BookOwl BookOwl mentioned this issue Apr 10, 2017
Open
@BookOwl
Copy link
Owner Author

BookOwl commented Apr 11, 2017

http://stackoverflow.com/questions/43237389/implementing-pipes-without-using-threads

@BookOwl
Copy link
Owner Author

BookOwl commented Apr 11, 2017

futures (and specifically streams) seem like a good way to do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BookOwl BookOwl

Labels
enhancement
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
1 participant
@BookOwl