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

Add "how to optimize parsers" documentation #130

Closed
jam1garner opened this issue Jun 1, 2022 · 0 comments
Closed

Add "how to optimize parsers" documentation #130

jam1garner opened this issue Jun 1, 2022 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@jam1garner
Copy link
Owner

jam1garner commented Jun 1, 2022

Spinning off from #129, making users more aware of this is a good practice.

Most notable things to be included:

  1. how buffering can help perf
  2. how seeks can affect binrw's perf characteristics
  3. how Vec<u8> is specialized
  4. how per-field error handling can add overhead in pathological cases

Also to be considered:

  1. perf debugging tool recommendations (strace, flamegraph)

(If anyone else has additions as to parts of the performance characteristics found to be unintuitive please comment them below)

@jam1garner jam1garner added the documentation Improvements or additions to documentation label Jun 1, 2022
@csnover csnover self-assigned this Aug 25, 2022
csnover added a commit to csnover/binrw that referenced this issue Aug 26, 2022
csnover added a commit to csnover/binrw that referenced this issue Aug 26, 2022
csnover added a commit to csnover/binrw that referenced this issue Aug 26, 2022
jam1garner pushed a commit that referenced this issue Aug 26, 2022
@jam1garner jam1garner moved this to Done in binrw 0.10.0 Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: Done
Development

No branches or pull requests

2 participants