westonpace commented on pull request #10240: URL: https://github.com/apache/arrow/pull/10240#issuecomment-837252021
@pitrou Another option would be to defer creation of jemalloc pool until starting up, allowing the user to override the jemalloc configuration with their own configuration. Exposes 0 new APIs but 1 new environment variable (i.e. `MALLOC_CONF`). That approach would also prevent the thread from ever being created (as opposed to this approach which allows it to be created only to immediately destroy it). However, I'm not sure what "starting up" would mean. We could create it when the default memory pool is first asked for (if it doesn't exist). If that seems cleaner I could implement that. -- 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
