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.
Hi
I have added the JSaPar parser to the comparison but I have not updated the readme with the result.
You find the parser project at https://github.com/org-tigris-jsapar/jsapar
I added two flavors of the parser, feel free to remove or comment out any of the two. The fastest one (JSaPar internal) does only the string splitting part while the slower (JSaPar) does a lot of additional stuff matching the input to a schema so that each cell can be retrieved by a name and by correct type instead of only as strings by it's position.
Feel free to squash the commits while merging if it is possible in GitHub.
I must add that this comparison project really triggered me to look into performance while parsing. The result was JSaPar version 2.0.1 where a lot of the internals was re-written in order to improve performance. Thanks.