Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18936
I don't see what that has to do with it. The threading setting only affects
what native code does. A single-thread configuration should be able to saturate
CPU, too. Allowing multiple threads on top of parallelism hurts because it's
introducing some pointless context switching.
What matters are benchmarks: Java vs native code with default settings. If
that's not much different, there's really no problem with this change. And
ideally the comparison is vs OpenBLAS.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
