Right now we're loading the whole file, and at some point this will impact usability.
- Generate fake CSVs, and vary:
- number of rows
- number of columns
- bit depth / data type
- Profile performance on:
- schema inference
- sampling (of public datasets)
- ...?
- Make sure none are super-linear.
- Figure out a way to do an early warning for large files: Just read as text and count
\n?
Right now we're loading the whole file, and at some point this will impact usability.
\n?