Re: Benchmarking MXNet with different compilers and different OpenMP implementations (results)

2019-04-12 Thread Pedro Larroy
Are there any updates on this? This is still affecting multiprocessing, some tests hang: rces. For information on submitting this issue, please see https://bugs.llvm.org/. [INFO] Setting test np/mx/python random seeds, use MXNET_TEST_SEED=2124604270 to reproduce. Assertion failure at

Re: Benchmarking MXNet with different compilers and different OpenMP implementations (results)

2019-02-14 Thread Tsukrov, Stanislav
Thanks Aaron for the feedback. > As for your next steps, would you propose that cmake be brought up to parity? Yes. sse2 in cmake vs sse3 in make is a minor example without high impact. There are others. > It seems strange that it causes slowness and if so, it shouldn't be > recommended for

Re: Benchmarking MXNet with different compilers and different OpenMP implementations (results)

2019-02-14 Thread Anton Chernov
Thank you, Aaron, for your interest on the topic. My main previous proposal still stands: remove bundled OpenMP submodule and use OpenMP provided by the environment [1]. This might lead to performance degradation in some cases where an old OpenMP library is used or thread affinity wasn't set

Re: Benchmarking MXNet with different compilers and different OpenMP implementations (results)

2019-02-12 Thread Aaron Markham
This is really great research. I've often wondered what the difference really is, and why it has to be so complicated. It seems the answer is there isn't much difference and it shouldn't be as complex. As for your next steps, would you propose that cmake be brought up to parity? It seems strange