daniel-adam-tfs opened a new issue, #540: URL: https://github.com/apache/arrow-go/issues/540
### Describe the enhancement requested We're testing reading parquet files from S3 and I'm looking at the memory profile. We're using a 2GB file for testing and in the profile I see that the `make` call in https://github.com/apache/arrow-go/blob/c8d24781add849d22169a27a8bd6d00a86fbdde1/parquet/reader_properties.go#L80 allocates about 2GB of data, which is about a third of the total allocations that our test that reads the whole file does. I see that the ReaderProperties has an allocator field, but the allocation there is made using the standard Go call. Is there a reason why the custom allocator is not used there? I wanted to test using a custom allocator, so maybe we can switch the `make` call to `r.alloc.Allocate` ? ### Component(s) Parquet -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
