docs(readme): refresh local parser benchmark results - #192
Merged
Conversation
abimaelmartell
marked this pull request as ready for review
August 1, 2026 04:50
Member
Author
|
fixes #191 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refreshes benchmark references across the root README, benchmarking guide, and Node, Python, and Rust documentation with new July 31, 2026 results for pdf-inspector, LiteParse, OpenDataLoader, PyMuPDF4LLM, and MarkItDown. The updated documentation records the five-run median timings and reevaluated quality scores, explains the single-process measurement protocol, and links to the opendataloader-bench branch containing the raw timings, parser configuration, predictions, evaluator output, and generated charts.