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

Feature: Leveraging Ropes for efficient IO operations such as text file parsing and indexing #10

Open
FlatlinerDOA opened this issue Nov 6, 2024 · 0 comments

Comments

@FlatlinerDOA
Copy link
Owner

A common practice when working with strings is parsing text from disk.
This feature set would look to provide convenience methods of efficiently parsing massive text files and network streams while minimising allocations and garbage collection. In addition to this the goal would be to provide infrastructure for indexing files using bloom filters.

Currently .NET provides ReadOnlySequence<T> for efficiently processing streams, but working with it correctly is difficult, unintuitive and poorly documented. The goal would be to provide higher level API's that still give a good compromise with regards to performance

Benchmarks to add

  • Rope based Csv Parser implementation compared vs Naive string split parsing technique vs ReadOnlySequence<T> parsing.
  • Bloom Filter indexed file search vs Brute force search
  • Time to index a large file vs Time to re-index a large file
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

1 participant