nevi-me commented on pull request #8796: URL: https://github.com/apache/arrow/pull/8796#issuecomment-735362452
> Perhaps unsurprisingly to you, but a bit to me, this leads to a significant improvement over almost all benches You can consider me surprised too. This is very interesting, can one then say that the alignment requirements from `arrow::memory` are the main cause of the difference? If we only enforce alignment at boundaries like IPC and FFI, could we still be able to use `Vec<u8>` internally? I don't think it should also be much of an issue for Parquet, as we currently materialise Arrow data into the primitives that Parquet supports, due to the way arrays are indexed for definition levels. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
