1. This assumes all your data fits in memory, or no?
2. How do you deal with I/O wait from the CPU for reading from disk and interacting line by line if it doesn't fit into your memory?
3. Isn't CSV as useful? Like many languages supports using the "header" of a CSV and generates a hash/array whatever based on those headers (defeating the purposing of parsing json back and forth).
4. Again, exporting as CSV is even faster, specially if you using PostgreSQL and you use "COPY" or MySQL "LOAD DATA INTO", cannot speak for sqlite though.
So I have a couple questions:
1. This assumes all your data fits in memory, or no?
2. How do you deal with I/O wait from the CPU for reading from disk and interacting line by line if it doesn't fit into your memory?
3. Isn't CSV as useful? Like many languages supports using the "header" of a CSV and generates a hash/array whatever based on those headers (defeating the purposing of parsing json back and forth).
4. Again, exporting as CSV is even faster, specially if you using PostgreSQL and you use "COPY" or MySQL "LOAD DATA INTO", cannot speak for sqlite though.
Thank you!