Python Pandas Ditches NumPy for Speedier PyArrow
thenewstack.io
Python Pandas Ditches NumPy for Speedier PyArrow
1–6 of 6 posts
Re: Python Pandas Ditches NumPy for Speedier PyArrow
#2[dead]
Re: Python Pandas Ditches NumPy for Speedier PyArrow
#3This is an insane article, I do not think the author has any idea what is going on.
The comparison of numpy reading CSV to arrow reading parquet is completely bizarre and totally misses the point of switching out the underlying data format.
Re: Python Pandas Ditches NumPy for Speedier PyArrow
#4> [numpy] stores everything in rows
This isn't true. Pandas uses Numpy to store columns of data. Theres quite a few technical errors in the article.
Re: Python Pandas Ditches NumPy for Speedier PyArrow
#5This is an insane article, I do not think the author has any idea what is going on. The comparison of numpy reading CSV to arrow reading parquet is completely bizarre and totally misses the point of switching out the underlying data format.
Or maybe you did not read it properly?
> Reading in that CSV file into memory would take Python 55.8 seconds, but PyArrow did the work in 11.8 seconds.
It's later clarified that Pyarrow does load csv here, though the numbers don't fully add up. Also the format change is explained.
Re: Python Pandas Ditches NumPy for Speedier PyArrow
#6It gets worse the further you go, this was where I had to bail:
> the format is much favored by AI frameworks such as TensorFlow and PyCharm.