josevalim
Hello everyone,
We have just released NimbleCSV which is a small and fast CSV parsing library for Elixir. It allows developers to define their own parsers so we can rely on binary patterns for efficiency reasons. It also supports dumping and data streaming. We hope this will be an excellent companies along side the efforts we have put on GenStage (and GenStage.Flow):
Docs: NimbleCSV v1.3.0 — Documentation
Source: GitHub - dashbitco/nimble_csv: A simple and fast CSV parsing and dumping library for Elixir · GitHub
Where Next?
Trending in Announcing
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
andre1sk
Amazing, how do you find the time to do everything?
benwilson512
Initial results indicate that NimbleCSV is 10x faster than CSV when parsing from a file stream, and 10x faster than ExCSV when parsing a literal string (ExCSV doesn’t do streams, CSV doesn’t do raw strings).
Will post full results in a bit, along with CSV writing benchmarks.
OvermindDL1
Oh that is great timing! I’m just about to need to parse CSV files from another system.
michalmuskala
I tried looking what would be the performance difference if the separators weren’t bound at compile-time. The difference looks to be more-or-less 1.6x, which is quite surprising - i though it would be much worse.
The code is here: GitHub - michalmuskala/nimble_csv at no-macro-magic · GitHub
While the difference for decoding is significant, the difference for encoding seems to be completely negligible.
OvermindDL1
Just looking at how to use it, it seems you build a module via: nimble_csv/lib/nimble_csv.ex at master · dashbitco/nimble_csv · GitHub
I am curious if there is planned to be a way to
useit into an existing module to turn that module into a parser? It would be useful to add helper functions and parsing module all in one without needing to delegate functions otherwise?Yeah the Beam VM has a lot of interesting things like that. I ended up making a math module about 6 years ago that got pretty fast after a lot of testing, a lot of weird things ended up being fast, and compile-time generation of structures was absolutely necessary for speed.
michalmuskala
It seems like a relatively bad idea. Each time you would
useit you’d generate all those functions leading to code bloat and long compilation times.OvermindDL1
True, though how many projects have many different styles of CSV parsing all at the same time?
ericmj
But that’s what the library does now anyway, it’s just hidden behind another macro. Using
usewould improve composability and you wouldn’t have to pass in the moduledocs as an option.michalmuskala
I think I misunderstood the initial question. Yes I think it might make sense to provide a “more traditional”
use-based interface.DianaOlympos
You have no idea… Never worked a lot with Perl dev haven’t you ?