-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Thanks for the traces, @chenrui17! For the first question, this appears to be within libcudf's Parquet decoder, as all the behavior in question occurs within that If you have configured a sufficient pinned memory pool for the SQL plugin, the buffer being handed to the libcudf parquet decoder will be pinned memory. Assuming you have configured enough pinned memory to hold the parquet data across the concurrent tasks, pageable transfers may be from CPU buffers computed within the libcudf call. For the second question about missing Java traces, cudf Java does not generate NVTX traces by default and will only do so if the system property |
Beta Was this translation helpful? Give feedback.
Thanks for the traces, @chenrui17!
For the first question, this appears to be within libcudf's Parquet decoder, as all the behavior in question occurs within that
read_parquet
sample within libcudf. If you have a small repro case, it would be great to file a question in the https://github.com/rapidsai/cudf project, or if you attach it here I can do the same.If you have configured a sufficient pinned memory pool for the SQL plugin, the buffer being handed to the libcudf parquet decoder will be pinned memory. Assuming you have configured enough pinned memory to hold the parquet data across the concurrent tasks, pageable transfers may be from CPU buffers computed within the libcudf call.
Fo…