[ 
https://issues.apache.org/jira/browse/ARROW-17399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17597400#comment-17597400
 ] 

Will Jones commented on ARROW-17399:
------------------------------------

Sorry, you are right you had a single column there already.

I tried your repro on my M1 Macbook and didn't see the memory usage you are 
seeing. (This is with mimalloc allocator, but I got similar results with 
jemalloc and the system allocator.)

Are you able to reproduce this on the latest versions of Pandas and Numpy? And 
could you confirm your package version numbers?

{code:none}
❯ python test_pyarrow.py
  0 time:       0.0 rss:      79.5
  1 time:       2.0 rss:     617.1
  2 time:       3.4 rss:    1090.6
  3 time:       3.7 rss:     633.6
  4 time:       6.7 rss:     633.6
  5 time:      10.1 rss:    1942.9
  6 time:      13.1 rss:    1942.9
  7 time:      13.6 rss:     664.8
  8 time:      16.6 rss:     664.8
{code}

> pyarrow may use a lot of memory to load a dataframe from parquet
> ----------------------------------------------------------------
>
>                 Key: ARROW-17399
>                 URL: https://issues.apache.org/jira/browse/ARROW-17399
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Parquet, Python
>    Affects Versions: 9.0.0
>         Environment: linux
>            Reporter: Gianluca Ficarelli
>            Priority: Major
>         Attachments: memory-profiler.png
>
>
> When a pandas dataframe is loaded from a parquet file using 
> {{{}pyarrow.parquet.read_table{}}}, the memory usage may grow a lot more than 
> what should be needed to load the dataframe, and it's not freed until the 
> dataframe is deleted.
> The problem is evident when the dataframe has a {*}column containing lists or 
> numpy arrays{*}, while it seems absent (or not noticeable) if the column 
> contains only integer or floats.
> I'm attaching a simple script to reproduce the issue, and a graph created 
> with memory-profiler showing the memory usage.
> In this example, the dataframe created with pandas needs around 1.2 GB, but 
> the memory usage after loading it from parquet is around 16 GB.
> The items of the column are created as numpy arrays and not lists, to be 
> consistent with the types loaded from parquet (pyarrow produces numpy arrays 
> and not lists).
>  
> {code:python}
> import gc
> import time
> import numpy as np
> import pandas as pd
> import pyarrow
> import pyarrow.parquet
> import psutil
> def pyarrow_dump(filename, df, compression="snappy"):
>     table = pyarrow.Table.from_pandas(df)
>     pyarrow.parquet.write_table(table, filename, compression=compression)
> def pyarrow_load(filename):
>     table = pyarrow.parquet.read_table(filename)
>     return table.to_pandas()
> def print_mem(msg, start_time=time.monotonic(), process=psutil.Process()):
>     # gc.collect()
>     current_time = time.monotonic() - start_time
>     rss = process.memory_info().rss / 2 ** 20
>     print(f"{msg:>3} time:{current_time:>10.1f} rss:{rss:>10.1f}")
> if __name__ == "__main__":
>     print_mem(0)
>     rows = 5000000
>     df = pd.DataFrame({"a": [np.arange(10) for i in range(rows)]})
>     print_mem(1)
>     
>     pyarrow_dump("example.parquet", df)
>     print_mem(2)
>     
>     del df
>     print_mem(3)
>     time.sleep(3)
>     print_mem(4)
>     df = pyarrow_load("example.parquet")
>     print_mem(5)
>     time.sleep(3)
>     print_mem(6)
>     del df
>     print_mem(7)
>     time.sleep(3)
>     print_mem(8)
> {code}
> Run with memory-profiler:
> {code:bash}
> mprof run --multiprocess python test_pyarrow.py
> {code}
> Output:
> {code:java}
> mprof: Sampling memory every 0.1s
> running new process
>   0 time:       0.0 rss:     135.4
>   1 time:       4.9 rss:    1252.2
>   2 time:       7.1 rss:    1265.0
>   3 time:       7.5 rss:     760.2
>   4 time:      10.7 rss:     758.9
>   5 time:      19.6 rss:   16745.4
>   6 time:      22.6 rss:   16335.4
>   7 time:      22.9 rss:   15833.0
>   8 time:      25.9 rss:     955.0
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to