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 management] investigate possible usage of System.IO.Pipelines in openMCDF API #26

Closed
michaelp opened this issue Jul 22, 2018 · 2 comments
Assignees
Labels
enhancement performance issues or enhancements related to the performance characteristics of the project

Comments

@michaelp
Copy link
Contributor

michaelp commented Jul 22, 2018

The following is a list of relevant resources, that IMO applicable to the current situation

  1. System.IO.Pipelines: High performance IO in .NET
  2. Also Span
  3. and obviously [post1] (https://blog.marcgravell.com/2018/07/pipe-dreams-part-1.html)
  4. [post2] (https://blog.marcgravell.com/2018/07/pipe-dreams-part-2.html)
@michaelp michaelp added enhancement performance issues or enhancements related to the performance characteristics of the project labels Jul 22, 2018
@michaelp michaelp changed the title [performance] [memory management] investigate possible usage of System.IO.Pipelines in openMCDF API [memory management] investigate possible usage of System.IO.Pipelines in openMCDF API Jul 22, 2018
@michaelp michaelp self-assigned this Jul 22, 2018
@jeremy-visionaid
Copy link
Collaborator

@michaelp I'm too not sure about how applicable Pipelines would be to CFB, since it's more random access data than it is streaming... As part of v3 in #194 I've rewritten things to be mostly based around enumerators with some caching, and added support for reading/writing Spans. It reduce the memory usage to just a few KB and mostly obtains better performance than the native COM based implementation.

@jeremy-visionaid
Copy link
Collaborator

I'm hopeful that 3.0.0-preview1 should get released to NuGet in the next few days. @ironfede has kindly granted me write access to the repo, so I'll go ahead and close this one as fixed by #194.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement performance issues or enhancements related to the performance characteristics of the project
Projects
None yet
Development

No branches or pull requests

2 participants