-
Notifications
You must be signed in to change notification settings - Fork 89
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
Make csvlint way faster #99
Merged
Merged
Conversation
This file contains 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
…is idiomatic and faster
Weird, no test failure locally. I'll try later on Ruby 2.0 (running 2.1). Update: Confirm works in 2.1 but not 2.0. Looking into it. |
I've got some more commits for more speed, but I don't want to overcomplicate this PR. (e.g. 12MB CSV takes ~10s, not ~230s). |
This is awesome. Thanks so much 😄 I'll review this in more detail and merge tomorrow if all's good 👍 |
Hurrah for open source! 🎆 |
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.
The speed gain is directly correlated to the size of the CSV. I tested on a 1.7MB CSV. These commits dropped its validation time from 9s to 1s. I used stackprof to identify bottlenecks. Main bottleneck now is Ruby's CSV library, though date format detection is still slow. I recommend reviewing one commit at a time. In brief:
With the new, fast version, the code spends time roughly as follows:
loop
inparse_csv
csv.shift
(previously 13%)build_formats
(previously 61%)build_errors
col_counts
(because Rails' String#blank? is slow)So, csvlint now spends a lot more time parsing CSVs (a cost we can't reduce) and less time rescuing exceptions (a cost I cut here).