GitHub user AnthonyTruchet opened a pull request: https://github.com/apache/spark/pull/15963
[SPARK-18471][MLLIB] In LBFGS, avoid sending huge vectors of 0 ## What changes were proposed in this pull request? CostFun used to send a dense vector of zeroes as a closure in a treeAggregate call. To avoid that, we replace treeAggregate by mapPartition + treeReduce, creating a zero vector inside the mapPartition block in-place. ## How was this patch tested? Unit test for module mllib run locally for correctness. As for performance we run an heavy optimization on our production data (50 iterations on 128 MB weight vectors) and have seen significant decrease in terms both of runtime and container being killed by lack of off-heap memory. You can merge this pull request into a Git repository by running: $ git pull https://github.com/criteo-forks/spark master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/spark/pull/15963.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #15963 ---- commit d5d110b8fc0d7165cce116c1e8342ce7aca2467b Author: Eugene Kharitonov <e.kharito...@criteo.com> Date: 2016-10-14T11:25:34Z [SPARK-18471][MLLIB] In LBFGS, avoid sending huge vectors of 0 CostFun used to send a dense vector of zeroes as a closure in a treeAggregate call. To avoid that, we replace treeAggregate by mapPartition + treeReduce, creating a zero vector inside the mapPartition block in-place. commit 7095bc2c568564ebc4584c1101cb94801079d1bd Author: Anthony Truchet <a.truc...@criteo.com> Date: 2016-11-18T12:36:00Z Style fix according to reviewers' feedback commit 011a8d77cac26f820c3cecda1c28e623a64f803b Author: Anthony Truchet <anthonytruc...@users.noreply.github.com> Date: 2016-11-21T12:26:10Z Merge pull request #11 from AnthonyTruchet/ENG-17719-lbfgs-only [SPARK-18471][MLLIB] In LBFGS, avoid sending huge vectors of 0 ---- --- 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