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

Memory usage #297

Open
snap9 opened this issue Feb 8, 2017 · 3 comments
Open

Memory usage #297

snap9 opened this issue Feb 8, 2017 · 3 comments

Comments

@snap9
Copy link

snap9 commented Feb 8, 2017

It looks like Conduit, in the case of lists, focuses on streaming data through a pipe one element at a time.

  • Does this mean the max memory use is (roughly) the memory size of each element in the list?
  • Do most people using Conduit just use the default 1-element approach and find it fast enough?
  • Can we customize the memory usage? For instance, make it stream 10 values at once. (I'm talking about doing so under the hood, even if it still looks like a 1-element stream to the programmer.) This would increase memory usage 10x but could improve execution time.
@snoyberg
Copy link
Owner

snoyberg commented Feb 12, 2017 via email

@snap9
Copy link
Author

snap9 commented Feb 12, 2017

@snoyberg Thanks for the tips. Just to clarify, you're suggesting I use [Vector a] instead of [a]. It would now be my responsibility to pack as many values as I want (for instance 10 values) into these vectors.

So it's not like conduit has some magic to pack more values. I'd have to do it myself using Vector, adjust the number of elements myself, and benchmark for myself which works best.

Am I understanding correctly?

@snoyberg
Copy link
Owner

snoyberg commented Feb 12, 2017 via email

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