Adding DFLib Java DataFrame to comparison #4
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 @mathijs81 ,
Found your Java DataFrame comparison blog recently. It is a pretty cool comparison, and I wanted to add one more contender : DFLib 🙂
DFLib is pure Java and provides immutable DataFrames and nice fluent transformations API (and Jupyter integration, and charts, etc.). While Tablesaw and Joinery seem dormant, DFLib is a very active project. This PR is based on the last public release (1.1.0). In 2.0, CSV loading will become speedier, once we switch away from Apache
commons-csv
, so the benchmark should become even better. But even with the slower CSV loader, DFLib is much faster than Tablesaw. In my test it was409.3
(TS) vs153.3
(DFLib).I can't fully build the
master
branch because of the specificjoinery
andkrangl
dependencies missing on Maven Central. But if you already have them locally, my PR should work for you. As far as the build goes, it switches Java to 11 (minimal DFLib requirement) and adds a single dependency.Would be great to see what numbers you end up with for DFLib on your side 🙂