[GitHub] [arrow] wjones127 commented on pull request #12286: ARROW-15408: [C++] Enable memory logging with env var

[GitBox <gi...@apache.org>]

wjones127 commented on pull request #12286:
URL: https://github.com/apache/arrow/pull/12286#issuecomment-1025817778


   > I am a bit skeptical about this. As you point out, this might only be useful for simple applications, otherwise I expect the traces to be too copious and lack too much context to be really of any help.
   
   Yeah it certainty seemed less useful once I saw the test output myself. I assumed that since someone put the effort to implement the logging pool it might be useful, and this change seemed like low-hanging fruit.
   
   > It may be more useful to invest time into optionally tracing memory allocations using our OpenTracing infrastructure, what do you think?
   
   I was planning on documenting next using perf to trace calls to the memory pool, but maybe open tracing would be more worthwhile. I'll look into 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.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org