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 Sylvan.Data.Csv to the benchmarks #4
Conversation
No, we didn't. I pulled the benchmarking code out of my main Sylvan library repo on that day. If you look in that repository you'd see history of this stuff going back to earlier in 2020. Still, pretty funny that date aligned. |
FWIW I added both |
give Sylvan a bigger buffer (to match competitors)
This might be considered "unfair" as it takes advantage of the construction of the test data. However, real-life datasets have shown significant savings here too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again!
Woah this thing is fast! I've updated my post: Nice work Mark! |
Hah, thanks! Anyway, thanks for updating the article. I'm trying to get some momentum behind this project, so every little bit of exposure is helpful. |
Hello Joel.
I've also also put together some CsvBenchmarks for .NET. I've been claiming that my library, Sylvan.Data.Csv, is the fastest, so I was curious how I stacked up with your dataset. This PR adds my library to your benchmarks. I was aware of NReco and how fast it was, but I hadn't seen this mgholam.FastCsv library. I'll add it to my benchmarks too. I'm also adding the FluentCsv to mine (not yet on github).