assignUser commented on PR #39522: URL: https://github.com/apache/arrow/pull/39522#issuecomment-1885237395
I build jemalloc with our release configure command and `make` vs `make -j1`: - `./test.sh 56.47s user 7.29s system 102% cpu 1:02.35 total` - `./test.sh 57.22s user 7.05s system 103% cpu 1:02.16 total` So it seems that make defaults to a mostly single core build anyway, this just removes issues we had. Explicitly passing -j16 to the jemalloc build interestingly also fixes the issue and does not show the warning mentioned in https://github.com/apache/arrow/pull/2779. It might be enough to remove that change/conditional. I have tested this on ubuntu 20.04 with cmake 3.16 and it also works there. (I think cmake decoupled external projects from the main make by adding a cmake layer inbetween at some point prior to 3.16). I'll open a PR. -- 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]
