Skip to content

Don't use enumerator in CSV#363

Open
kou wants to merge 1 commit into
ruby:mainfrom
kou:each-enumerator
Open

Don't use enumerator in CSV#363
kou wants to merge 1 commit into
ruby:mainfrom
kou:each-enumerator

Conversation

@kou

@kou kou commented Jul 24, 2026

Copy link
Copy Markdown
Member

GitHub: Fix GH-361

CSV::Parser#parse can continue from the previous state.

Reported by Cas Donoghue. Thanks!!!

GitHub: Fix rubyGH-361

CSV::Parser#parse can continue from the previous state.

Reported by Cas Donoghue. Thanks!!!
Copilot AI review requested due to automatic review settings July 24, 2026 22:28

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@donoghuc donoghuc left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing thanks. Running on jruby this is back to good performance.

@kou

kou commented Jul 25, 2026

Copy link
Copy Markdown
Member Author

Thanks for checking performance on JRuby. Could you also check regression with your application's test suite? If there is no regression, I'll merge this and release a new version.

@donoghuc

Copy link
Copy Markdown

Ran the test suites locally for the following plugins (all passing with your change)

I also tested this with a sample logstash pipeline and observed a 10x speedup in events per second flowing through the system (from about 8.5k -> 92k). This is great. thanks for the quick turnaround.

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

Successfully merging this pull request may close these issues.

JRuby performance regression for CSV.parse_line

3 participants