That opening gave me a pause too.
Doesn't Pandas target only structured (tabular) in-core datasets? (Unless you use something like Blaze / Dask / Ray on top.)
Does anyone really work with Pandas on "100's of terabytes of biological data"?
Re:Pandas on Ray – Make Pandas faster
by thewizardofaus on Saturday March 03, 2018 @04:40PM
(#16511763)
Yeah, I tend to use modified hdf5 tools for data that big.
Re:Pandas on Ray – Make Pandas faster
by sfsylvester on Saturday March 03, 2018 @07:14PM
(#16512510)
This is exactly my go-to-move as well.
pandas.read_hdf has beaten out ray.dataframe.read_csv in terms of speed on the few files I've just initially tested now. But I imagine the programmable flexibility csvs have over hdfs (I've never used a Unix command to edit a hdf for example) is why this new approach could get some traction.
Try parquet if your data is tabular, pyarrow and related tools are getting parquet up to a pretty comparable speed to hdf5, with arguably more flexibility and a better multithreading story.
"biological data" is a bit vague, but for the data I know to be that big, sequence and array data, it does not naturally have the structure of a dataframe nor is pandas the tool of choice.